From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 90A761F4C0; Wed, 16 Oct 2019 22:10:45 +0000 (UTC) Date: Wed, 16 Oct 2019 22:10:45 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: how's memory usage on public-inbox-httpd? Message-ID: <20191016221045.GA6828@dcvr> References: <20181201194429.d5aldesjkb56il5c@dcvr> <20190606190455.GA17362@chatter.i7.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190606190455.GA17362@chatter.i7.local> List-Id: Konstantin Ryabitsev 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.