<div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small">On Thu, Jan 30, 2025 at 6:32 AM Ronald Barnes via kwlug-disc <<a href="mailto:kwlug-disc@kwlug.org" target="_blank">kwlug-disc@kwlug.org</a>> wrote:</div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It's now quite clear: mm2 uses 9 process and < 50 MB RAM, but MM3 uses <br>
17+12=29 processes (and that's with the default NNTP bridge disabled), <br>
and 889.9+182.4=1072.3 MB RAM.<br>
<br>
That's a *lot* of Python processes!<br></blockquote><div><br></div><div style="font-size:small" class="gmail_default">I am reminded of our discussion on this group about (October last year) about <br></div><div style="font-size:small" class="gmail_default">having lean software and avoiding bloat. <br></div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">If the functionality is still the basic set (mail group + users adding and removing </div><div style="font-size:small" class="gmail_default">themselves, archive of threads), then using over 20X the RAM is totally unwarranted.</div><div style="font-size:small" class="gmail_default"><br></div><div style="font-size:small" class="gmail_default">There is so much CPU and RAM, and SSDs are much faster than HDDs, that many</div><div style="font-size:small" class="gmail_default">(most?) developers don't bother to optimize anymore. <br></div><br></div></div>
</div>