Andrew Sawyers wrote:
The other engineer was me, and it was close enough to double the load
per instance, per cpu.
tangential question: I'm assuming you were using LVS in front of these
boxes? If so, how'd you get the both clients on the box accessible by
LVS? 2 ip addresses?
cheers,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Andrew Sawyers wrote:
The other engineer was me, and it was close enough to double the load
per instance, per cpu.
tangential question: I'm assuming you were using LVS in front of these
boxes? If so, how'd you get the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dario Lopez-Kästen wrote:
snip
Let me be the first to admit my total lack of knowledge of kernel task
schedulers, but generally speaking, unless the scheduler makes sure that
a threaded python process never ever gets distributed over two
On Wed, 2006-03-22 at 08:24 -0500, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
WHile at ZC, one of the other engineers and I did some testing on SMB
boxes, and found that one appserver per CPU gave us near linear
scaling of the application, without any explicit
