From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:45126) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jBfiq-00029w-57 for guix-patches@gnu.org; Tue, 10 Mar 2020 10:19:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jBfip-0000mJ-83 for guix-patches@gnu.org; Tue, 10 Mar 2020 10:19:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:47037) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jBfio-0000iJ-5G for guix-patches@gnu.org; Tue, 10 Mar 2020 10:19:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jBfio-0007MQ-0b for guix-patches@gnu.org; Tue, 10 Mar 2020 10:19:02 -0400 Subject: [bug#39258] [PATCH v2 0/3] Xapian for Guix package search Resent-Message-ID: From: Arun Isaac In-Reply-To: <87r1y13jew.fsf@gnu.org> References: <20200307133116.11443-1-arunisaac@systemreboot.net> <87sgijgb1v.fsf@gnu.org> <875zffcc87.fsf@gnu.org> <87r1y13jew.fsf@gnu.org> Date: Tue, 10 Mar 2020 19:47:57 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: mail@ambrevar.xyz, 39258@debbugs.gnu.org, zimon.toutoune@gmail.com --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > Note that Texinfo rendering doesn=E2=80=99t use (@ (guix ui) fill-paragra= ph). > It has its own paragraph-filling code. We cannot use =E2=80=98fill-parag= raph=E2=80=99 > after Texinfo rendering anyway, since Texinfo knows where things can be > filled and where they cannot=E2=80=94e.g., @example. True, I did not think of this. > We could provide a substitute for users who use only the official 'guix > channel. However, as soon as users combine multiple channels, they=E2=80= =99ll > have to build the index locally. We could build a separate Xapian database for each channel. Xapian does support searching across multiple databases at once and will handle merging the results together appropriately. If I understand correctly, this means we can provide substitutes for at least the official guix channel and let the user build the index locally for other channels. Is that correct? Also, could someone please build the patchset v2 on their machine and measure the time taken by generate-package-search-index? My laptop, particularly my HDD is slow even as far as HDDs go. So, my figure of 20-50 seconds may not be representative. Thanks, Arun. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl5noZUACgkQLiXui2GA K7Nw9gf/b/wKWyQ4b6s7K0/oUeiQOOY54Mg45SpV58vTQs3/n97iLOmhEDsRUoJL QjSpl/BwbpeyjQTeAToBom6UT2QW0rWQ/x4DOlCeFnBlL6LFhGvkNEptHFb2ag7G OpgdO+ljsgO5BkFlU31HvHbe7wLZ7KWSmREXWOw3enGymQD6e/VdDUZz71AwMx/c 95SCGtEY2wKUc0ZceBsgPr7+LyHCQ3h3ga+SX/G9HFyJ5/rU2+7ytzjri6oXaDXJ vWycwBmvutrNZASSuZ/XZaLy7nnK9HWpYABPiiKUTsYei62WtVyiTvzDkFpI0kkY G8Qn7VU6ZJ95cZb4lY60ETYbgdsnnw== =fOJU -----END PGP SIGNATURE----- --=-=-=--