mass unsubscribe is far to slow
Bug #265594 reported by
Lkoeller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Invalid
|
Medium
|
Unassigned |
Bug Description
We have mailing lists with more than 20000 members, an
the
subscription of an empty list is very fast (<2 min).
When we try to delete this list with
..../bin/
it took several hours. We stop it after 14 min where
still more than
19000 users are subscribed.
My currently workaround is to set the arrays
members
passwords
user_options
per config_list to nil. This only took 7 seconds. A new
fill of the list
is still as fast as above after this.
Is it possible to handle the -a flag in remove_members
in a special case
for speed up?
Thanks and best regards
Lars
[http://
To post a comment you must log in.
This is caused by the self.Save() in MailList.py's
DeleteMember() method. In 2.0.x Mailman tries to save the
list database after each member is deleted instead of doing
all the deletes first and then saving the list.
Sadly, I will likely not fix this in the 2.0.x series. It
is already fixed in Mailman 2.1.