From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: trying to figure out 100% CPU usage in nntpd...
Date: Wed, 11 Sep 2019 17:12:40 +0000 [thread overview]
Message-ID: <20190911171239.xkclzeszibtmlxl3@dcvr> (raw)
In-Reply-To: <20190911094435.GB3548@pure.paranoia.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Tue, Sep 10, 2019 at 06:12:24PM +0000, Eric Wong wrote:
> > Any git-http-backend stuck from people fetching/cloning?
>
> No, all git processes seem to exit cleanly on both ends.
>
> > This is -httpd writing to varnish, still, right?
>
> We bypass varnish for git requests, since this is not generally useful.
> Nginx goes straight to public-inbox-httpd for those.
>
> I did run some updates on lore.kernel.org on Thursday, including kernel
> (3.10.0-957.27.2), nginx (1.16.1) and public-inbox updates. For the
> latter, it went from f4f0a3be to what was latest master at the time
> (d327141c).
I also noticed "tcp: remove empty skb from write queue in error cases"
(64a2a93ba3856d16765e5c8a00c133fa8750879a) which is likely to affect
public-inbox using edge-triggered epoll. Not sure if
Linux 3.10.0-957.27.2 has that backported...
Also, what nginx buffer settings are you using? In particular,
is proxy_buffering off or on? Also, does that version of nginx
do persistent connections to backends (and if so, is it enabled)?
It doesn't seem pipe-user-pages related, but what I wrote could
definitely be a problem in the future with the number if inboxes
you have and I should be able to mitigate that by alternates
and sharing a cat-file process.
prev parent reply other threads:[~2019-09-11 17:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 10:45 [PATCH] nntp: regexp always consumes rbuf if "\n" exists Eric Wong
2019-09-08 10:52 ` trying to figure out 100% CPU usage in nntpd Eric Wong
2019-09-09 10:05 ` Konstantin Ryabitsev
2019-09-09 17:53 ` Eric Wong
2019-09-10 8:38 ` Konstantin Ryabitsev
2019-09-10 18:12 ` Eric Wong
2019-09-11 2:22 ` httpd 502s [was: trying to figure out 100% CPU usage in nntpd...] Eric Wong
2019-09-11 10:24 ` Konstantin Ryabitsev
2019-09-11 17:12 ` Eric Wong
2019-09-11 17:36 ` Konstantin Ryabitsev
2019-09-12 0:05 ` Eric Wong
2019-09-12 2:49 ` Eric Wong
2019-09-12 8:35 ` Eric Wong
2019-09-12 11:37 ` Konstantin Ryabitsev
2019-09-13 3:12 ` Eric Wong
2019-09-13 7:03 ` Eric Wong
2019-09-13 9:01 ` Eric Wong
2019-09-13 18:07 ` Konstantin Ryabitsev
2019-09-14 5:25 ` Eric Wong
2019-09-11 9:44 ` trying to figure out 100% CPU usage in nntpd Konstantin Ryabitsev
2019-09-11 17:12 ` Eric Wong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190911171239.xkclzeszibtmlxl3@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).