Hi List
I have a (bit aged) Redhat 9 box (Pentium II/512Mb RAM) running Mailman 2.1.6 with Postfix. Its only has to run a single moderated mailing list sending out one email every day to around 20,000 subscribers.
Sending out the emails is not problem - it works great. The major problem is logging in to approve the email. It (Apache/2.0.40) is so slow that it usually times out with a 500 error after you try and login.
Is there a way of speeding up the web interface? Can I approve postings from the command line?
There is a large archive as they have been running this for around 3 years. Will it speed up if we trash part of the archive. If so how can I trash archived data that is (say) over a year old?
There was a thread on this problem, but it was not really resolved, and that user had 450,000 subscribers.
Any help appreciated.
Jon Harris
Jon Harris wrote:
Can I approve postings from the command line?
If you set admin_immed_notify to Yes on the list's General Options page, the admin will receive an e-mail notification of each pending approval which gives instructions for approving or discarding the post by e-mail. Not exactly command line approval, but it does avoid the web interface.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I am looking into ways to improve performance for our mailman server. It currently serves 15,000 mailing list, and the largest list has more than 10,000 members. We are running mailman 2.1.8 with Postfix. We have load spike at 20, and during busy hours, load average is around 10. Messages delays do occur but not too bad yet. I want to be more proactive to prevent things from getting worse.
Mailman FAQ 6.6 mentioned the following configuration tuning for qrunner:
|Set your qrunner proc to live longer, and extend the lock life:
|QRUNNER_LOCK_LIFETIME = hours(10) |QRUNNER_PROCESS_LIFETIME = minutes(15) |QRUNNER_MAX_MESSAGES = 300 |Set these to 20 hours, 2 hours and 50000
I cannot find these variables used anywhere in source code, other than mentioned in NEWS file in the mailman release.
Thanks in advance for your help,
Xueshan
Xueshan Feng wrote:
Mailman FAQ 6.6 mentioned the following configuration tuning for qrunner:
|Set your qrunner proc to live longer, and extend the lock life:
|QRUNNER_LOCK_LIFETIME = hours(10) |QRUNNER_PROCESS_LIFETIME = minutes(15) |QRUNNER_MAX_MESSAGES = 300 |Set these to 20 hours, 2 hours and 50000
These are Mailman 2.0.x settings. They aren't relevant to Mailman 2.1.x.
Unfortunately, there's a lot of old stuff in the FAQ.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Jon Harris -
Mark Sapiro -
Xueshan Feng