From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Baines Subject: Re: Guix size reduction work group Date: Mon, 10 Feb 2020 08:46:46 +0000 Message-ID: <87blq625jd.fsf@cbaines.net> References: <87pneul50i.fsf@ambrevar.xyz> <87blqdnjuv.fsf@gnu.org> <875zghdo7j.fsf@ambrevar.xyz> <87r1z2c17u.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39450) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j14iT-0008Al-PT for guix-devel@gnu.org; Mon, 10 Feb 2020 03:46:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j14iS-00023L-HG for guix-devel@gnu.org; Mon, 10 Feb 2020 03:46:53 -0500 In-reply-to: <87r1z2c17u.fsf@ambrevar.xyz> 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-mx.org@gnu.org Sender: "Guix-devel" To: Pierre Neidhardt Cc: Guix Devel --=-=-= Content-Type: text/plain Pierre Neidhardt writes: > zimoun writes: > >> You could propose such feature to the Guix Data Service. >> For example, on this webpage [1], the history of all the Git package >> in Guix is shown. The closure size could be reported. >> >> [1] http://data.guix.gnu.org/repository/1/branch/master/package/git > > This is a great idea! Christopher, what do you think? I don't think adding to that particular page is feasible, but I think having a page just of this information would be great :) I'm not quite sure how that would work, but the Guix Data Service can query for narinfo files, and from those it can store the size of specific outputs, as well as there references. So the closure size (I think?) is the size of an output, plus the closure size of all of its references (the definition is recursive). Then you could compute the closure size for the output (or set of outputs) for a package, and then graph that over the different revisions on a branch. Because this is using information from builds, it's a little complicated by the information potentially varying between build server, for example, if the nar non-deterministically includes a reference. Going back to the point about preventing regressions though, there I think it would be good to enhance the comparision functionality of the Guix Data Service so that it can compare derivation outputs, and say how the closure size has changed. Then you could look at this when reviewing patches. Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEPonu50WOcg2XVOCyXiijOwuE9XcFAl5BGHZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcACgkQXiijOwuE 9XfMvhAAptMgDc0j+Meg38s38PqLlqDEY9KQ9KszVDbNe36lWvusQWjcYpJCikEM rjzcB/Zpkyra+oGPXNd5As7cTA0Cuv4YWN622g+iecdscE570P8ZoALPhmG1J/qo 8Wji4Z2hnHNbx/GWs31xMgGIEHngS2vMN/sLk23/RYGL9wiymXotVCprEnebFoJd g2xGQ6Cg3jiFzrsJDKSvwUnSNwFtFk9ASLbJSutRPa1lYfPeoUx59jj8i3ZpWGdC gHWRUo7jbwSZSDPvooVhqJ8LPTgn2ESqJ9LBksmkrN0PUyYIWW/0bBTg0qjtGbUg Ojz74tdzG8W2+e6CfFvITzTI/IfzVr2ePkWMwmRfTjXOX3RKUCmXm3E7JSj33zCM YJrTfSCm3FqlPrgviSbLEE49mdLx725oHAK9QJeiWy0wfVlmNZgLCXP7rhWxwMv1 po485SBuUDbsj2MYyIEQ9rfpaW65PQhpzz2/HZwW9DEU9CbD8cwD4Yr4zNysTACw QV/q49tu26UYv2/B9Wchnsq2493bu8RkexKBjf/O0Xf2AU7PIsNiOXYepAqcW0ef WCspK/LDLQL83PxNqDvBxOBb8FM/SSRpVylsDam/N5NDsQHOthCSgAHBKEq+C+bW 4O+Urf7uZaaS8xmXarvd46Qn2adZ143I1WR/whCTOf5YNJanrx4= =H8YL -----END PGP SIGNATURE----- --=-=-=--