Thanks again for the speedy support.
The only (occasional) error message is that archiving failed ("archiving
failed, re-queuing (mailing-list ...") but none of the above Mark mentioned.
What is suspicious though is that uwsgi is at the top of the list of CPU slice
consumers. Which may point at a problem with the REST-based communication
between HK and MM.
Postgres only consumes roughly 5% of available CPU bandwidth but I'll review
Greg's suggestions to see if these make any difference.
_______________________________________________
Mailman-users mailing list -- mailman-users@mailman3.org
To unsubscribe send an email to mailman-users-le...@mailman3.org
https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Archived at:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/2JRHIL5TVUWR5TRLUKUTZ2PSGP2T2HKO/
This message sent to arch...@mail-archive.com
