netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: potential patchwork accuracy problems..
Date: Fri, 9 Aug 2024 21:25:08 -0700	[thread overview]
Message-ID: <20240809212508.02617159@kernel.org> (raw)
In-Reply-To: <20240809091738.GG3075665@kernel.org>

On Fri, 9 Aug 2024 10:17:38 +0100 Simon Horman wrote:
> On Thu, Aug 08, 2024 at 08:54:15AM -0700, Jakub Kicinski wrote:
> > Minor heads up that updating state in patchwork is agony, lately.
> > I think people are building more and more CI systems, and patchwork
> > can't handle the write load. So I get timeouts trying to update patch
> > state 2 of of 3 times. NIPA is struggling, too, but at least it has
> > auto-retry built in..
> > 
> > So long story short if something seems out of whack in patchwork,
> > sorry, I'm doing my best :(  
> 
> Do you know if someone who can address the problem is aware of it?

I have emailed, and offered help. Didn't see a reply.

> My anecdotal experiences is that access has been degraded, on and off,
> for a few months.

Yes, in the past Konstantin was able to chase down the bad actors, 
I think, as well as do some backend magic to improve the DB performance.
But it keeps happening, and patchwork has no built in protection.
(I need to find some weekend time to parse our own logs and graph 
the number of requests we send to make triple sure NIPA is behaving.)

      reply	other threads:[~2024-08-10  4:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 15:54 potential patchwork accuracy problems Jakub Kicinski
2024-08-09  9:17 ` Simon Horman
2024-08-10  4:25   ` Jakub Kicinski [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

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

  git send-email \
    --in-reply-to=20240809212508.02617159@kernel.org \
    --to=kuba@kernel.org \
    --cc=horms@kernel.org \
    --cc=netdev@vger.kernel.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 NNTP newsgroup(s).