From: Aaron Conole <aconole@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
ci@dpdk.org, Dumitru Ceara <dceara@redhat.com>
Subject: Re: Question about pw-ci behavior
Date: Tue, 09 Dec 2025 09:47:08 -0500 [thread overview]
Message-ID: <f7ttsxzbtlf.fsf@redhat.com> (raw)
In-Reply-To: <81a3f76a-abfd-4cf3-8b6d-717a76f88205@nvidia.com> (Ali Alnubani's message of "Tue, 9 Dec 2025 12:13:58 +0200")
Ali Alnubani <alialnu@nvidia.com> writes:
> Hello Aaron,
>
> I wanted to share some more statistics,
>
> I see that requests with the pw-ci user agent are making 3,200–4,200
> requests per hour (approximately 50–70 requests per minute).
> This volume appears excessive and places strain on the Patchwork server.
>
> Would you be able to check if polling frequency can be adjusted?
I'm adding a few things. NOTE that pw-ci marks the series as done when
the states are 'finished' in the status details. But for example the
listed series is still in a 'valid' state for polling.
I'm going to set it to mark for superceding the patches that are expired
by 30 days. That should reduce the polling here. Just had to deal with
a different issue on redirects with a different patchwork server (so I
added some new code).
> On 12/8/25 4:36 PM, Ali Alnubani wrote:
>> Hello Aaron, I hope you're well,
>>
>> I noticed that pw-ci (patches.dpdk.org) is making repeated Patchwork
>> API requests to very old and inactive series IDs. Example:
>>
>> """
>> 66.187.232.140 - - [08/Dec/2025:00:16:48 +0100] "GET /api/series/25093/ HTTP/1.1" 200 1351 "-" "(pw-ci) pw-mon-"
>> 66.187.232.140 - - [08/Dec/2025:00:36:07 +0100] "GET /api/series/25093/ HTTP/1.1" 200 1351 "-" "(pw-ci) pw-mon-"
>> [..]
>> 66.187.232.140 - - [08/Dec/2025:14:16:48 +0100] "GET /api/series/25093/ HTTP/1.1" 200 1351 "-" "(pw-ci) pw-mon-"
>> 66.187.232.140 - - [08/Dec/2025:14:37:25 +0100] "GET /api/series/25093/ HTTP/1.1" 200 1351 "-" "(pw-ci) pw-mon-"
>> 66.187.232.140 - - [08/Dec/2025:15:01:48 +0100] "GET /api/series/25093/ HTTP/1.1" 200 1351 "-" "(pw-ci) pw-mon-"
>> 66.187.232.140 - - [08/Dec/2025:15:17:13 +0100] "GET /api/series/25093/ HTTP/1.1" 200 1351 "-" "(pw-ci) pw-mon-"
>> """
>>
>> Is this expected/necessary?
Yes, because these series have weird state - they are missing patches,
so patchwork is holding them in a waiting state. I'll add the
auto-clear code and hopefully that will reduce the amount of outstanding
patches we poll.
>> Thanks,
>> Ali
next parent reply other threads:[~2025-12-09 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ2PR12MB91923047B6BB780DAD91D459DAA2A@SJ2PR12MB9192.namprd12.prod.outlook.com>
[not found] ` <81a3f76a-abfd-4cf3-8b6d-717a76f88205@nvidia.com>
2025-12-09 14:47 ` Aaron Conole [this message]
2025-12-09 15:07 ` Aaron Conole
2025-12-09 16:15 ` Aaron Conole
2025-12-09 16:29 ` Ali Alnubani
2025-12-09 19:47 ` Aaron Conole
2025-12-10 9:07 ` Ali Alnubani
2025-12-09 16:53 ` Thomas Monjalon
2025-12-09 19:46 ` Aaron Conole
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=f7ttsxzbtlf.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=dceara@redhat.com \
--cc=thomas@monjalon.net \
/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).