Dear all,

I've been using mailman2 for quite some time and I am considering upgrading to mailman3. In a test setup I noticed that mailman3 with just a basic setup (Debian with mailman3 package and sqlite as backend using exim4) uses over 700MB RAM (RSS): | USER VSZ RSS COMMAND | list 73072 54568 /usr/bin/python3 /usr/lib/mailman3/bin/master | list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=archive:0:1 | list 73100 54572 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=bounces:0:1 | list 73100 54560 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=command:0:1 | list 73100 54600 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=in:0:1 | list 146832 54700 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=lmtp:0:1 | list 73100 54808 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=nntp:0:1 | list 73100 54652 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=out:0:1 | list 73100 54504 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=pipeline:0:1 | list 150516 58228 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=rest:0:1 | list 73100 54508 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=retry:0:1 | list 73100 54500 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=virgin:0:1 | list 73100 54608 /usr/bin/python3 /usr/lib/mailman3/bin/runner --runner=digest:0:1 This is with only one test list configured that just has one member. Compared to a mailman2 setup with many lists with up to 300 members that only uses around 70MB RAM: | USER VSZ RSS COMMAND | list 63724 1396 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -q start | list 62896 10660 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s | list 61156 1792 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s | list 58148 1808 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s | list 73116 23316 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s | list 55464 1672 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s | list 65840 11868 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s | list 62036 10840 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s | list 58716 5712 /usr/bin/python /var/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s This is without hyperkitty or a management interface, just mailman3 core that uses 10 times as much ram as mailman2. Did I do something wrong here? Is there probably a bug in my python environment? Are there any config options that I should set to avoid this huge memory footprint?

I found one thread[1] on this mailing list where a user asked a question similar to mine with comparable numbers.

best regards, Adi Kriegisch

[1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...