Nothing in the TextPipe help file mentions multi-core processors, yet there must be a strong probability that TextPipe uses multi-threading, else why would there be a need for a Restrict to each line in turn filter?
I'm beginning to wonder whether some of the recent problems I've encountered are caused by TextPipe's software algorithms and how these operate in a dual-core system.
TextPipe originated in the days when personal computers were generally single core.
The only reference in the help file to multiple CPUs is in the page for Switch CPU.
Found under Filters\Special (Server Edition Only)
This filter causes a logical break in the processing from one CPU to another. It allows processing load to be distributed across multiple CPUs.
For example, if a filter list involved data preparation, sorting, and then output generation, then it makes sense to have the sorting on one CPU alone, as sorting is very CPU intensive.
Start by placing the splitter roughly in the middle of the filter list – before or after a sort typically. Then try moving it up and down to gauge performance.
Note: The numeric field of this filter is currently unused.
Each time you use this filter, a new logical processing thread is created. Windows takes care of distributing this thread to the CPU with the least load.