From: Ali Alnubani <alialnu@nvidia.com>
To: Aaron Conole <aconole@redhat.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: Wed, 10 Dec 2025 11:07:40 +0200 [thread overview]
Message-ID: <9efb4439-5d2c-438b-8035-2c9bb397943f@nvidia.com> (raw)
In-Reply-To: <f7tsedja148.fsf@redhat.com>
On 12/9/25 9:47 PM, Aaron Conole wrote:
> Ali Alnubani <alialnu@nvidia.com> writes:
>
>> On 12/9/25 6:15 PM, Aaron Conole wrote:
>>
>>> Aaron Conole <aconole@redhat.com> writes:
>>>
>>>> Aaron Conole <aconole@redhat.com> writes:
>>>>
>>>>> 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).
>>>>>
>>>> BTW, following is the patch I'm testing out right now just for the 'old'
>>>> ones:
>>>>
>>> I've added a date check to the patch as well, and am locally testing it.
>>> When it looks right, I'll push and there will be one last "large" query
>>> and that should check the dates and expire the outstanding series that
>>> we poll against.
>>>
>> Thank you for helping with this and for the updates,
> I pushed it live. I hope this cools off the requests.
I’m seeing a 60–70% reduction in requests per hour — thank you again for
your help with this.
Regards,
Ali
next prev parent reply other threads:[~2025-12-10 9:09 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
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 [this message]
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=9efb4439-5d2c-438b-8035-2c9bb397943f@nvidia.com \
--to=alialnu@nvidia.com \
--cc=aconole@redhat.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).