From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Re: [Cuirass] Missing database indexes? Date: Mon, 19 Nov 2018 10:47:17 +0100 Message-ID: <7b09e1f9-d91a-b604-42ed-1a8a255c2811@riseup.net> References: <87va54yh0c.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36117) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gOg3i-0005R4-Bf for guix-devel@gnu.org; Mon, 19 Nov 2018 04:41:34 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gOg3e-000615-DW for guix-devel@gnu.org; Mon, 19 Nov 2018 04:41:34 -0500 Received: from mx1.riseup.net ([198.252.153.129]:45761) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gOg3c-0005yT-GE for guix-devel@gnu.org; Mon, 19 Nov 2018 04:41:28 -0500 Received: from piha.riseup.net (piha-pn.riseup.net [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 649661A01EE for ; Mon, 19 Nov 2018 01:41:24 -0800 (PST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by piha.riseup.net with ESMTPSA id B01F11E041A for ; Mon, 19 Nov 2018 01:41:23 -0800 (PST) In-Reply-To: <87va54yh0c.fsf@gnu.org> Content-Language: en-US List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org Hi On 2018-11-10 18:33, Ludovic Court=C3=A8s 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=20 table for every jobset? This would also solve the problem with=20 overrunning id. (there will never be more ids than jobs in a single=20 jobset in a table) This means cuirass only work on one database per specification (now=20 there are 5 specs on berlin) Every jobset having its own table/file will lower the total number of=20 rows, thus lower the computing cost of a table scan. --=20 Cheers Swedebugia