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-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 BB5761F4C0 for ; Tue, 22 Oct 2019 17:28:34 +0000 (UTC) Received: by mail-qt1-x835.google.com with SMTP id m15so28021580qtq.2 for ; Tue, 22 Oct 2019 10:28:34 -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=n2R5hNn8cSEImnH6JVO6l9VOBqShqLSoyihVru/6mW0=; b=P5shh0Hhd3wDR+7kcYxPf71wX3PGqBv6wGFmrGRhpfTh4itnjYTW+KMqEDwAMa2YWN Ti2/Q56xzJisepxo+SVXnCPKSPw8PiKsWAGrwcZVLAMk6Vo9bB6cRrNJYYHaC58Z9Lwq tyb3F6lyfcZxMprsaFXLOWF8a3yeF2sx13ofo= 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=n2R5hNn8cSEImnH6JVO6l9VOBqShqLSoyihVru/6mW0=; b=kkmEVC7LaG5sAlwVHmQIIkPKKSrxNCNua/I/7+x1nPrSvusUuL/NhNkOgwCgcEUwT1 aKP1In13cze5RyNzLsF6exNDuowBPUMHPJ1qnE2+UOGR7s0y1cWdnoCHaF/9E8RnGbAR ff1tQbpEweqBWeULCKmjOtikZCqNv8vi0HntT3CDI/5mPsXzKWgvE3U9W1HRirUgaUS1 uAmYfIT+M+HdapcyBtvOTWo5htfpgzLVH58MUldAKCC+uC6gNt2UqO672kB4b/LGqRdw AWF8nL14WbKFQJKlk8r9BdjuHID9rEshFfr6l/tKliF0uGCg+tVtumhHdtWy4nAmRMW1 NADg== X-Gm-Message-State: APjAAAVHz554c+dorje73cVziMeeRO17p7M+00Z/HEceIxjexTOS3kdK Ijt0CHIdpfvqYhYO3GshofMXfg== X-Google-Smtp-Source: APXvYqw39+IKtHH7VPesyS4f6SlHFGp9SZXOj1fpd/zCQNSAn6dGP4ndKrAldiyMttkX6CqmmnsEog== X-Received: by 2002:ac8:7557:: with SMTP id b23mr4584838qtr.288.1571765313424; Tue, 22 Oct 2019 10:28:33 -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 f37sm9095394qtb.65.2019.10.22.10.28.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Oct 2019 10:28:32 -0700 (PDT) Date: Tue, 22 Oct 2019 13:28:30 -0400 From: Konstantin Ryabitsev To: Eric Wong Cc: meta@public-inbox.org Subject: Re: how's memory usage on public-inbox-httpd? Message-ID: <20191022172830.GB4960@chatter.i7.local> References: <20181201194429.d5aldesjkb56il5c@dcvr> <20190606190455.GA17362@chatter.i7.local> <20191016221045.GA6828@dcvr> <20191018192352.GH25456@chatter.i7.local> <20191019001144.GA20824@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <20191019001144.GA20824@dcvr> User-Agent: Mutt/1.12.1 (2019-06-15) List-Id: On Sat, Oct 19, 2019 at 12:11:44AM +0000, Eric Wong wrote: >> 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. > >Cool, but 1GB is still an order of magnitude worse that what >I'd expect :< I remember Email::MIME had huge explosions with >some 30MB+ spam messages: > https://public-inbox.org/meta/20190609083918.gfr2kurah7f2hysx@dcvr/ > (maybe gmime can help) > >Depending on your storage speed/latency, more RAM can still help >significantly with Xapian. The NVME stuff has amazing numbers, >but my mobos are too old and I'm still stuck on SATA 2. My goal is to rework lore.kernel.org significantly. Currently, it's a single system hosted at AWS that both receives mail and serves the archives, but I would actually like to split it into two: - the archiver that just generates git repositories but serves no traffic (probably running directly on mail.kernel.org). - several front-ends that replicate repositories from the archiver and provide http/nntp access, probably reusing mirrors.edge.kernel.org nodes that run from us-west, us-east, eu-west and ap-east. That should provide both redundancy and better geographic availability of the service. This requires some testing first to ensure that grokmirror hooks and reindexing works reliably for replicated repo collections. >Is nntpd better? That only uses Email::Simple and not MIME; >so less explosions. The number of people using nntp is several orders of magnitude lower, so I'm not sure it's a good metric for anything. Best, -K