Konstantin Ryabitsev <konstan...@linuxfoundation.org> wrote: > Hello: > > This is an old-ish discussion, but we finally had a chance to run the httpd > daemon for a long time without restarting it to add more lists, and the > memory usage on it is actually surprising: > > $ ps -eF | grep public-inbox > publici+ 17741 1 0 52667 24836 8 May24 ? 00:00:00 /usr/bin/perl > -w /usr/local/bin/public-inbox-nntpd -1 /var/log/public-inbox/nntpd.out.log > publici+ 17744 17741 0 69739 90288 9 May24 ? 00:38:43 /usr/bin/perl > -w /usr/local/bin/public-inbox-nntpd -1 /var/log/public-inbox/nntpd.out.log > publici+ 18273 1 0 52599 23832 9 May24 ? 00:00:00 /usr/bin/perl > -w /usr/local/bin/public-inbox-httpd -1 /var/log/public-inbox/httpd.out.log > publici+ 18275 18273 4 5016115 19713872 10 May24 ? 13:59:13 /usr/bin/perl > -w /usr/local/bin/public-inbox-httpd -1 /var/log/public-inbox/httpd.out.log > > You'll notice that process 18275 has been running since May 24 and takes up > 19GB in RSS. This is a 16-core 64-GB system, so it's not necessarily super > alarming, but seems large. :) > > Is that normal, and if not, what can I do to help troubleshoot where it's > all going?
Btw, has this gotten better since the Perl 5.16.3 workarounds? My 32-bit instance which sees the most HTTP traffic hasn't exceeded 80M per-process in a while. -- unsubscribe: meta+unsubscr...@public-inbox.org archive: https://public-inbox.org/meta/
