FWIW, at a former company we were running something like 20 Zope instances on a quad Xeon machine with impressive results. No "hanging" or anything like it to report. Note that an important tuning point is the system's checkinterval. Once we had this set to a high enough value CPU binding proved completely unnecessary and even counterproductive, YMMV. Stefan On 11. Mär 2005, at 23:05, Fernando Lujan wrote:
Tres Seaver wrote:
It is our experience in hosting Zope on SMP Linux boxen (2.4 series kernles) that the CPU scheduler will tend to migrate the Python processes to separate CPUs, without need for explicit binding.
Hi Tres,
So, Do I create 4 instances of Zope to use with a dual Xeon HT? :-)
-- Software Engineering is Programming when you can't. --E. W. Dykstra