From: Ilya Maximets <i.maximets@ovn.org>
To: Aaron Conole <aconole@redhat.com>, ci@dpdk.org
Cc: i.maximets@ovn.org, Michael Santana <msantana@redhat.com>,
Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [PATCH v3 2/2] post_pw: Store submitted checks locally as well
Date: Tue, 23 Jan 2024 11:49:05 +0100 [thread overview]
Message-ID: <52cc1db2-2b36-4375-aced-842f9ed089aa@ovn.org> (raw)
In-Reply-To: <20240122234034.3883647-3-aconole@redhat.com>
On 1/23/24 00:40, Aaron Conole wrote:
> Jeremy Kerr reports that our PW checks reporting submitted 43000 API calls
> in just a single day. That is alarmingly unacceptable. We can store the
> URLs we've already submitted and then just skip over any additional
> processing at least on the PW side.
>
> This patch does two things to try and mitigate this issue:
>
> 1. Store each patch ID and URL in the series DB to show that we reported
> the check. This means we don't need to poll patchwork for check status
>
> 2. Store the last modified time of the reports mailing list. This means
> we only poll the mailing list when a new email has surely landed.
>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
> ---
> v2: fixed up the Last-Modified grep and storage
> v3: Simplified the logic of creating the last-access file
>
> post_pw.sh | 35 ++++++++++++++++++++++++++++++++++-
> series_db_lib.sh | 25 +++++++++++++++++++++++++
> 2 files changed, 59 insertions(+), 1 deletion(-)
Didn't test, but seems correct. Thanks!
Best regards, Ilya Maximets.
next prev parent reply other threads:[~2024-01-23 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 23:40 [PATCH v3 0/2] Reduced checks API usage Aaron Conole
2024-01-22 23:40 ` [PATCH v3 1/2] treewide: Add a User Agent for CURL requests Aaron Conole
2024-01-23 10:47 ` Ilya Maximets
2024-01-22 23:40 ` [PATCH v3 2/2] post_pw: Store submitted checks locally as well Aaron Conole
2024-01-23 5:49 ` Michael Santana
2024-01-23 10:49 ` Ilya Maximets [this message]
2024-01-23 13:46 ` [PATCH v3 0/2] Reduced checks API usage 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=52cc1db2-2b36-4375-aced-842f9ed089aa@ovn.org \
--to=i.maximets@ovn.org \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=jk@ozlabs.org \
--cc=msantana@redhat.com \
/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).