unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: 32548@debbugs.gnu.org
Subject: bug#32548: Cuirass: Performance monitoring
Date: Sun, 06 Sep 2020 16:42:37 +0200	[thread overview]
Message-ID: <87d02zge5e.fsf@gnu.org> (raw)
In-Reply-To: <87pny3783p.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 28 Aug 2018 00:33:30 +0200")


Hello,

> As discussed earlier today on IRC with Clément, we could add performance
> monitoring capabilities to Cuirass.  Interesting metrics would be:
>
>   • time of push to time of evaluation completion;
>
>   • time of evaluation completion to time of build completion.

Small update on that one. With Cuirass commit
154232bc767d002f69aa6bb1cdddfd108b98584b, we now have the following
timestamps:

* Checkout commit time.
* Evaluation creation.
* Evaluation checkouts completion.
* Evaluation completion.

For the first timestamp, I'm using Guile-Git to extract the commit time,
which is not the commit push time. In fact, I think there is no such
thing as "commit push time" in git.

We can still compute the metric 'time of commit to time of evaluation
completion', but it's less relevant than the proposed 'time of push to
time of evaluation completion'.

The other proposed metric, 'time of evaluation completion to time of
build completion' can now be computed.

Regarding the actual computation and reporting of those metrics, I'm
still considering different options. I'd like to have a look to
Guile-prometheus that is written by Christopher.

Thanks,

Mathieu




  reply	other threads:[~2020-09-06 14:43 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 [this message]
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
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=87d02zge5e.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=32548@debbugs.gnu.org \
    --cc=ludo@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).