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: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 7EB011F4C1 for ; Fri, 18 Oct 2019 19:23:57 +0000 (UTC) Received: by mail-qt1-x82f.google.com with SMTP id r5so10743165qtd.0 for ; Fri, 18 Oct 2019 12:23:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=3TOqxG1WqE9RaNDKVK7Io/R2WxvaLy3IQUo+hlzaC7w=; b=ePitUaPGcQLckArroC1IsnqXwfBRN37hwocwmprh2avX2ui1vdHbj4//ln3HafbsOm SIVRHzQ4hGy0kRrxkzOK5pvhiqT0yGcgIWzLXVNQZlDYiPOTAYLSVODE4QXmLrDVVzVe trDhmgUhGV/fZ/cVUaDZe6fRrs03VfCqRsEW4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=3TOqxG1WqE9RaNDKVK7Io/R2WxvaLy3IQUo+hlzaC7w=; b=LpxqiF3svizu7Y1bWgniiI23zajLxnQLQQ2TmX6P+C6HdoxGzUu/8mGXITjYKqhJ4z IiF2R5IgeovQ0zHPz4jc6EhZMatB2pxBJ0TnWtzU28ChR5tQEVNVCV8E6vOe5qvy+xuV mzEMD8wKvsihMtqxvGqU0J/3dUZEfJ7k1201Te9bfg74JxDTER1yKDK4q+rtEdHBfWVU pJskqLZa8PZs+FOVW4anMcDICTfcKZCOZ9giWTeKJY/BBesP4MNggItjAj4FxHNtnUWb Dpeay6oVDJ4jVy6J5CK8Z24oEjtb26fJUZuph1yOU1RJedCsu4h/MNfWpudXwr2iXCdS eH4A== X-Gm-Message-State: APjAAAUIUedDOk6qpfaUzF9ff85efh19IqQrBbNXMqj2Vgh9zbYwDPOa Ck13OIJVUgTuvsCe9GgeusgXxA== X-Google-Smtp-Source: APXvYqxIOmhV8TC7xUqDZEdZeqQYD+0NJe7RdRzCyyu9OnS3pZpJ4UPAjfL+FXt4fbvU/Svv7yfuIA== X-Received: by 2002:ac8:3408:: with SMTP id u8mr11787223qtb.380.1571426636041; Fri, 18 Oct 2019 12:23:56 -0700 (PDT) Received: from chatter.i7.local (192-0-228-88.cpe.teksavvy.com. [192.0.228.88]) by smtp.gmail.com with ESMTPSA id 63sm3616151qkh.82.2019.10.18.12.23.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 18 Oct 2019 12:23:54 -0700 (PDT) Date: Fri, 18 Oct 2019 15:23:52 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: how's memory usage on public-inbox-httpd? Message-ID: <20191018192352.GH25456@chatter.i7.local> References: <20181201194429.d5aldesjkb56il5c@dcvr> <20190606190455.GA17362@chatter.i7.local> <20191016221045.GA6828@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <20191016221045.GA6828@dcvr> User-Agent: Mutt/1.12.1 (2019-06-15) List-Id: On Wed, Oct 16, 2019 at 10:10:45PM +0000, Eric Wong wrote: >> 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. It's been definitely dramatically better. We keep adding lists to lore, so I haven't really been able to watch memory usage after a long period of daemon uptime, but it's never really gone very much above 1GB. In fact, we're downgrading lore to a smaller instance in the near future since we don't need to worry about running out of RAM any more. Best, -K