From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org
Subject: Re: [Cuirass] Missing database indexes?
Date: Mon, 19 Nov 2018 10:47:17 +0100 [thread overview]
Message-ID: <7b09e1f9-d91a-b604-42ed-1a8a255c2811@riseup.net> (raw)
In-Reply-To: <87va54yh0c.fsf@gnu.org>
Hi
On 2018-11-10 18:33, Ludovic Courtès wrote:
snip
> --8<---------------cut here---------------start------------->8---
> sqlite> CREATE INDEX Builds_index_evaluation ON Builds(evaluation);
snip
> Anything else we should do?
I woke up today with an idea. :)
Now on berlin it seems that all jobset are in one enormous table, correct?
How about creating a database/sqlite file for every specification and a
table for every jobset? This would also solve the problem with
overrunning id. (there will never be more ids than jobs in a single
jobset in a table)
This means cuirass only work on one database per specification (now
there are 5 specs on berlin)
Every jobset having its own table/file will lower the total number of
rows, thus lower the computing cost of a table scan.
--
Cheers
Swedebugia
prev parent reply other threads:[~2018-11-19 9:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 17:33 [Cuirass] Missing database indexes? Ludovic Courtès
2018-11-10 20:11 ` Björn Höfling
2018-11-11 17:06 ` Ludovic Courtès
2018-11-12 18:50 ` Björn Höfling
2018-11-12 19:42 ` Amirouche Boubekki
2018-11-12 23:27 ` Danny Milosavljevic
2018-11-14 11:14 ` Ludovic Courtès
2018-11-16 22:31 ` Björn Höfling
2018-11-13 8:10 ` Clément Lassieur
2018-11-16 22:42 ` Björn Höfling
2018-11-12 23:31 ` Danny Milosavljevic
2018-11-13 0:04 ` Danny Milosavljevic
2018-11-14 11:11 ` Ludovic Courtès
2018-11-19 10:44 ` Danny Milosavljevic
2018-12-19 22:45 ` Amirouche Boubekki
2018-11-19 9:47 ` swedebugia [this message]
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=7b09e1f9-d91a-b604-42ed-1a8a255c2811@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.