unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 43850@debbugs.gnu.org
Subject: bug#43850: cuirass: inconsistent SQL queries execution time.
Date: Mon, 26 Oct 2020 23:59:51 +0100	[thread overview]
Message-ID: <87blgo8ufs.fsf@gnu.org> (raw)
In-Reply-To: <87blguzdig.fsf@gnu.org> (Mathieu Othacehe's message of "Thu, 22 Oct 2020 13:49:43 +0200")

Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

>> I have now copied the database to a tmpfs mounted directory to make sure
>> that those inconsistent duration are only caused by the I/O pressure on
>> berlin.
>
> This helps a lot. The Cuirass web service has been running smooth since
> two days, without any inconsistent query times.

Interesting.

> I'm considering using a tmpfs backed database for good. The problem is
> that we would need a save/restore mechanism in case Berlin
> reboots.

Hmm sounds risky, no?

I wonder if we could instead ensure no I/O-intensive workload runs that
machine.  I’m thinking in particular of the derivations that produce
ISO/qcow images that are not offloaded but maybe should.

WDYT?  Do you think that’d be enough?  Or is tmpfs our only hope?

Thanks,
Ludo’.




  reply	other threads:[~2020-10-26 23:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 16:04 bug#43850: cuirass: inconsistent SQL queries execution time Mathieu Othacehe
2020-10-14 16:53 ` Mathieu Othacehe
2020-10-20 11:45   ` Mathieu Othacehe
2020-10-22 11:49     ` Mathieu Othacehe
2020-10-26 22:59       ` Ludovic Courtès [this message]
2020-10-27  9:28         ` Christopher Baines
2020-10-27 14:10           ` Mathieu Othacehe
2020-10-27 18:11             ` Mathieu Othacehe
2021-03-25 12:46               ` Mathieu Othacehe
2020-10-31  4:33             ` Maxim Cournoyer
2020-11-01 18:23               ` Mathieu Othacehe

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=87blgo8ufs.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=43850@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).