moritz both writes:
Since my migration from mm2 to mm3 I see what I consider high loads and excessive i/o and memory usage.
This isn't informative enough to guess whether this is unusual for Mailman 3 or not.
My guess is that the main problem is the database backend for mailman, posterious and hyperkitty, which is sqlite. The database is >200MB at the moment (I have not found out why it is so huge,
I don't know how active your users are, but my mbox-format INBOX is currently just over 200MB with 1770 messages in it. I religiously prune out attachments (all of them, not just "big ones"), but it your lists are at all active, I wouldn't be surprised at that size of HyperKitty archive.
I don't know how HyperKitty handles attachments offhand, but I don't think they would be in the database itself; presumably they would be stored in separate files.
I take any recommandation for this situation. My current idea is changing the database backend to something else, i.e. mysql.
Either MySQL or PostgreSQL is a much better solution for a production server, at least from the point of view of CPU. I'm not sure about I/O or memory.
If you go the MySQL route, be aware that a while back there were some issues with record size and with Unicode. I'm not sure the versions you specify have those fixed. You can fix them yourself by tweaking the MySQL configuration; ask us if you prefer this, somebody will help (sorry, I don't remember details and need to go to a meeting).
but the "loaddata" command fails. The stack trace is below. Unfortunatelly, I have close to no knowledge of django and don't know why the Email matching query not exists.
I will come back to this after meetings if someone doesn't beat me to it.
Steve