user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Cc: Konstantin Ryabitsev <>
Subject: Re: httpd 502s [was: trying to figure out 100% CPU usage in nntpd...]
Date: Sat, 14 Sep 2019 05:25:09 +0000	[thread overview]
Message-ID: <20190914052509.5quscvb5x42pu6co@dcvr> (raw)
In-Reply-To: <20190913180732.GA3654@pure.paranoia.local>

Konstantin Ryabitsev <> wrote:
> On Fri, Sep 13, 2019 at 03:12:12AM +0000, Eric Wong wrote:
> > > No, it's just vanilla what comes with the source.
> > 
> > OK, and Perl 5.16.3 from CentOS 7?  (4:5.16.3-294.el7_6 RPM)
> Correct, though another thing that may help is the git version -- we
> install git2u from IUS, so the git version is not what is in standard
> CentOS7 (it's too ancient).
> # rpm -q git2u
> git2u-2.16.5-1.ius.centos7.x86_64
> See if you have more luck reproducing the problem when you get that in
> place. You should be able to find what you need by searching for "git2u
> ius centos".

Tried git2u, didn't help.  I wouldn't expect external processes
such as nginx or git-http-backend having any impact on leaks
unless it's slower/faster and triggers a race in public-inbox.

At this point I suspect it's timing-related in our code but
maybe not something my hardware/VM is capable of reproducing.

What level of parallelism is grokmirror using?

I am very curious if anybody else sees it, too...

> My access over the next 10 days is going to be spotty due to travel, but
> I'll try to catch up at least once a day.

The /proc fdinfo of the eventpoll descriptor+lsof at the same
time would be helpful if you get a moment.  But it's understandable
if you don't :>

> Thanks again for your help!

No problem.  I've gone through the code again but nothing jumped
out at me.  Will add some comments and dig into it again after
I do some other stuff.

Enjoy your travels!

  reply	other threads:[~2019-09-14  5:25 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 [this message]
2019-09-11  9:44           ` trying to figure out 100% CPU usage in nntpd Konstantin Ryabitsev
2019-09-11 17:12             ` Eric Wong

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190914052509.5quscvb5x42pu6co@dcvr \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).