The Mailman queue runners load your entire list into memory for all operations. So yes, that is normal for Mailman. I originally attempted to manage an announce only list with over 150,000 members on a 1.5GB Redhat but had to give up because these tasks grew to over 130MB each. I am currently running a 230,000 subscriber announce list split into 76 sub lists controlled by an umbrella list. No indivdual list is greater than 5k-6k. This all operates thorough a set of python and bash scripts I wrote to control subscriptions and unsubscriptions for the sublists ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
