Question about pw-ci behavior

Ali Alnubani alialnu at nvidia.com
Wed Dec 10 10:07:40 CET 2025


On 12/9/25 9:47 PM, Aaron Conole wrote:

> Ali Alnubani <alialnu at nvidia.com> writes:
>
>> On 12/9/25 6:15 PM, Aaron Conole wrote:
>>
>>> Aaron Conole <aconole at redhat.com> writes:
>>>
>>>> Aaron Conole <aconole at redhat.com> writes:
>>>>
>>>>> Ali Alnubani <alialnu at 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


More information about the ci mailing list