You can get very good load spread over multiple CPUs by running one pike process for every CPU you want to utilize. It's actually one of the better ways of getting pike to put as much CPU to use as possible.
/ Johan Sundström (Achtung Liebe!)
Previous text:
2004-02-01 13:12: Subject: Re: Default backend and thread backends?
On Sun, Feb 01, 2004 at 11:25:01AM +0100, Fredrik (Naranek) Hubinette (Real Build Master) @ Pike (-) developers forum wrote:
I've tried doing that. But it turns out that Pike would become less than half as fast in the process, so the effort was pretty much self- defeating.
Why not just create separate interpreter object (state) for every thread, and leave thread management (mutexes, IPCs, etc) to an app?
Another alternative would be object locks, function locks, etc (an attribute like "locked"?).
If I've SMP machine (and this becomes common nowadays, at least for servers), it makes sense.
But I guess it would require very extensive rewriting of interpreter, or?
Regards, /Al
/ Brevbäraren