Nope, here's an excerpt (one message) from the thread:
This machine is used exclusively for processing large VFP batches. It has a gig of Ram and a raid 5 array. I guarantee there is no streaming music or video, no intensive graphics on it. I do notice that before the second processor large processes would drive the processor up to 100% utilizations -- so I guess it was just disk activity that was hitting the processor that hard.The thread is an interesting one and well worth reading. Even more important is remembering its content.
Cheers
>more than likely, the additional processor freed up some other non-vfp bottlenecks so that everything ran faster (unless it was a vfp mtdll..)
>>>>Can Visual Foxpro benefit from multiple-processor machines?
>>>
>>>A VFP app itself is single-threaded, and therefore will only benefit in that the OS can offload some work to other processors.
>>
>>So how does that explain...Thread #
472486???
>>
>>
>>
>>>
>>>However, you can create multi-threaded VFP COM DLLs that will use all processors on the box. I regularly pound the stuffing out of VFP MTDLLs on my big quad box, at a rate of over a million hits per day, and they work great.