From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6EDBE46FF2; Tue, 9 Dec 2025 17:15:11 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1FE9C40689; Tue, 9 Dec 2025 17:15:11 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 5E5274067D for ; Tue, 9 Dec 2025 17:15:09 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1765296908; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MVPgb4h+rNAxLwEBh6b0AQyRAB+eYXLPq1vkh9dbWUQ=; b=E/Y2GXWr8+3NL1ASHeb9ngKluHxfHh7UK/G+B8HoQ9MllO5/GQ6TZiU0hsrFw69DqL1Xk4 Ma6xETKUIGCXGOvrI3yWnn7Tfc4BQu1APN7w4uLvTyGw+llSaFMreco0qsZ6KEP31GRpGm RK9/Huuwq6ecVcaJF5HRRTHgRJTcrGQ= Received: from mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-604-WZi-uaBJMwOMcgvQj2KxlQ-1; Tue, 09 Dec 2025 11:15:07 -0500 X-MC-Unique: WZi-uaBJMwOMcgvQj2KxlQ-1 X-Mimecast-MFC-AGG-ID: WZi-uaBJMwOMcgvQj2KxlQ_1765296906 Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 4D21D19560A5; Tue, 9 Dec 2025 16:15:06 +0000 (UTC) Received: from RHTRH0061144 (unknown [10.22.65.86]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 49C811956095; Tue, 9 Dec 2025 16:15:05 +0000 (UTC) From: Aaron Conole To: Ali Alnubani Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" , ci@dpdk.org, Dumitru Ceara Subject: Re: Question about pw-ci behavior In-Reply-To: (Aaron Conole's message of "Tue, 09 Dec 2025 10:07:22 -0500") References: <81a3f76a-abfd-4cf3-8b6d-717a76f88205@nvidia.com> Date: Tue, 09 Dec 2025 11:15:03 -0500 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: keoQaVGN7hwcSQD7rTgENlRHsfuW8CHZ9tXjLSchI0U_1765296906 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Aaron Conole writes: > Aaron Conole writes: > >> Ali Alnubani writes: >> >>> Hello Aaron, >>> >>> I wanted to share some more statistics, >>> >>> I see that requests with the pw-ci user agent are making 3,200=E2=80=93= 4,200 >>> requests per hour (approximately 50=E2=80=9370 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.