[Twisted-Python] Spawning processes and multiple CPU's.
corydodt at twistedmatrix.com
Thu Sep 2 11:57:53 EDT 2004
-----BEGIN PGP SIGNED MESSAGE-----
Basically, Twisted can't guarantee that the kernel will use both CPU's. But
if the CPU would normally put the process on the other CPU, then it will.
That you're using spawnProcess to start the process doesn't make any difference.
Matt Feifarek wrote:
| Yes, I agree that it's a candidate. Does it work that way?
| Does spawnProcess take advantage of multiple CPU's?
| On Wed, 01 Sep 2004 11:42:11 -0700, Cory Dodt
| <corydodt at twistedmatrix.com> wrote:
|>The invocation of an imagemagick process is certainly a candidate for the
|>kernel to put on a different CPU. Indeed, that's one of the biggest
|>advantages of using spawnProcess instead of (well, lots of other things).
|>Matt Feifarek wrote:
|>| I'm using reactor.spawnProcess to perform some inherently-blocking
| Twisted-Python mailing list
| Twisted-Python at twistedmatrix.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Twisted-Python