We have noticed similar slowness when importing/creating/deleting lists. We have ~2600 lists and the bottleneck does seem to be the MTA alias code that reads from backend (sorts by domain and then listnames?) and subsequently writes the (lmtp,vmap,etc) files.
We're running AWS aurora serverless DB on the backend and have split core/web hosts. Our setup is a bit different than most on this list probably, but for now we've resorted to setting:
incoming: mailman.mta.null.NullMTA
on the web boxes (not core) and actually rebuild the aliases every X minutes (X=15 for now) in a rundeck job. Testing the creation/deletion of lists now take ~5 seconds vs 3+minutes when Mailman was trying to re-generate the aliases on every create/delete. An obvious downside is the X delta out of sync-ness between Mailman and your MTA.
Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator
From: dancab@caltech.edu <dancab@caltech.edu> Sent: Tuesday, October 19, 2021 1:41 PM To: mailman-users@mailman3.org Subject: [MM3-users] Re: Mailman import of 2000 lists
Thank you. I will test this on my "dev/test" system to see how the performance improves for the mass import. We are also using the API for creating "new" lists and notice there's significant delay for creating just one list due to the nearly 2000 existing lists.
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mail...