Re: [Mailman-Users] Mailman does everything except send mail
barry@zope.com (Barry A. Warsaw) wrote on mailman-users:
MM2.1's qrunner will take almost no resources to just leave it running.
Is there a way to start say a hundred of them on the same box (in order to service a hundred separate Mailman installations) so that most of the memory is shared?
Greetings, Norbert.
-- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com
"NB" == Norbert Bollow nb@thinkcoach.com writes:
>> MM2.1's qrunner will take almost no resources to just leave it
>> running.
NB> Is there a way to start say a hundred of them on the same box
NB> (in order to service a hundred separate Mailman installations)
NB> so that most of the memory is shared?
You can start lots of them, even multiple ones to service the same queue. They won't collide and don't need to lock any resource.
But each is a separate Python process, in the current scheme of things. If the qrunners were I/O bound, you might see some gains by multithreading them, but I haven't implemented that at all (and it won't help if they're cpu bound).
-Barry
On May 25, 2002 at 15:59, Barry A. Warsaw wrote:
[qrunners]
You can start lots of them, even multiple ones to service the same queue. They won't collide and don't need to lock any resource.
So on a busy server, starting multiple qrunners from cron would help with the stale lockfile and associated issues?
-- Satya. URL:http://satya.virtualave.net/ 2 + 2 = 5 for extremely large values of 2.
[qrunners]
You can start lots of them, even multiple ones to service the same queue. They won't collide and don't need to lock any resource.
So on a busy server, starting multiple qrunners from cron would help with the stale lockfile and associated issues?
Barry was speaking about Mailman 2.1 there, you don't start the qrunners from cron in Mailman 2.1
In Mailman 2.0.x when you start a second qrunner for the same Mailman installation, the new qrunner will just exit. This doesn't help you.
(In the possibly-pretty-unique situation that I have, with _many_ Mailman 2.0.x installs per server, it's a bad idea to start those multiple qrunners directly from cron.)
Greetings, Norbert.
-- A founder of the http://DotGNU.org project and Steering Committee member Norbert Bollow, Weidlistr.18, CH-8624 Gruet (near Zurich, Switzerland) Tel +41 1 972 20 59 Fax +41 1 972 20 69 http://norbert.ch List hosting with GNU Mailman on your own domain name http://cisto.com
participants (3)
-
barry@zope.com
-
Norbert Bollow
-
Satya