>>>>You can change that by setting the
process affinity, in windows
SetThreadAffinityMask and
SetProcessAffinityMask, not sure if it is implemented in ParallelFox as I never used it (well, I never used the affinity mask myself anyways :)).
>>>
>>>Wow, OK. This sets a whole another level of control and complexity. I will need to save this for future investigation. But, it does answer my original question. Threads are spawned to the best available processor at the time they are initiated. But there is a way to control where they can be executed. I do agree that it is wiser to leave this to the system.
>>
>>Which is exactly what I posted earlier....
>
>Yes, you did. It just took me a bit of time to get my head around it.
Using those calls can eliminate cache trashing to press the last bit of speed out of the alternative approach described earlier: each longtime running worker handling db-based tasks runs on its own core, eliminating unnecessary switches betwenn the vfp tasks. net speed win minimal in my workloads...