From: zimoun <zimon.toutoune@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 32548@debbugs.gnu.org
Subject: bug#32548: Cuirass: Performance monitoring
Date: Mon, 14 Sep 2020 16:10:14 +0200 [thread overview]
Message-ID: <CAJ3okZ3TA-xnm1+nS_qxmjkeat=B+GETHrQ6PoV2YXSH9Q_c-A@mail.gmail.com> (raw)
In-Reply-To: <87tuw05vom.fsf@gnu.org>
Hi Mathieu,
Really cool!
On Mon, 14 Sep 2020 at 15:35, Mathieu Othacehe <othacehe@gnu.org> wrote:
> * Builds per day
> * Average evaluation speed per specification.
Something interesting could be: min and max (of 100 evaluations).
The standard error deviation too but I am not sure it is easy to
interpret with a quick look. Instead, the median could be
interesting.
For example, consider these 2 evaluations:
https://ci.guix.gnu.org/build/2094496/details
https://ci.guix.gnu.org/build/3035986/details
Well, if there is say 99 evaluations of first "kind" and 1 of second
kind, the average is:
(99*849 + 1_595_796_252) / 100 = 15_958_803.03
which does not really represent the effective workload.
Well, I will try to give a look if I can schedule a moment. :-)
> Those metrics can now be seen at:
>
> https://ci.guix.gnu.org/metrics
Nice plot!
> I plan to add more metrics such as:
>
> - Evaluation completion percentage.
> - Evaluation completion speed.
> - Failed evaluations percentage.
> - Pending builds per day.
Cool!
Maybe time between commit time (not author time) and start of the build.
Cheers,
simon
next prev parent reply other threads:[~2020-09-14 14:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 22:33 bug#32548: Cuirass: Performance monitoring Ludovic Courtès
2020-09-06 14:42 ` Mathieu Othacehe
2020-09-06 18:51 ` Christopher Baines
2020-09-07 8:11 ` Ludovic Courtès
2020-09-10 13:26 ` Mathieu Othacehe
2020-09-14 13:34 ` Mathieu Othacehe
2020-09-14 14:10 ` zimoun [this message]
2020-09-16 2:21 ` Bonface M. K.
2020-09-14 19:27 ` Ludovic Courtès
2020-09-17 10:07 ` Mathieu Othacehe
2020-09-17 20:22 ` Ludovic Courtès
2020-09-16 15:56 ` Andreas Enge
2020-09-17 7:10 ` Mathieu Othacehe
2020-09-18 12:21 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ3TA-xnm1+nS_qxmjkeat=B+GETHrQ6PoV2YXSH9Q_c-A@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=32548@debbugs.gnu.org \
--cc=othacehe@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).