From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7830 invoked from network); 14 Oct 2004 16:26:36 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 14 Oct 2004 16:26:36 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CI8Qh-0006b2-TL for arch-gentoo-dev@lists.gentoo.org; Thu, 14 Oct 2004 16:26:19 +0000 Received: (qmail 1347 invoked by uid 89); 14 Oct 2004 16:24:39 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 20972 invoked from network); 14 Oct 2004 16:24:38 +0000 From: Luke-Jr To: Gentoo Developers , gentoo-dev@lists.gentoo.org Date: Thu, 14 Oct 2004 16:24:40 +0000 User-Agent: KMail/1.7.1 References: <20041012223725.6c42698a@snowdrop.home> <20041013090106.7e2fe14b.spider@gentoo.org> <20041013073134.GB30671@curie-int.orbis-terrarum.net> In-Reply-To: <20041013073134.GB30671@curie-int.orbis-terrarum.net> IM-Address: luke-jr@jabber.org Public-GPG-Key-URI: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xD53E9583 Public-GPG-Key: 0xD53E9583 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1553956.AjqLMcc6OV"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410141624.43853.luke-jr@utopios.org> Subject: Re: [gentoo-dev] A few modest suggestions regarding tree size X-Archives-Salt: d83c4648-c23a-4809-9c65-ba40bfec3bed X-Archives-Hash: fa5116459b24444b90fb0a356ea4f02f --nextPart1553956.AjqLMcc6OV Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 13 October 2004 7:31 am, Robin H. Johnson wrote: > portage loop file is usually on disk, when a sync is needed: > 1. umount loop file > 2. copy loop file to /dev/shm or other fast place > 3. mount loop file again (from new location) > 4. run updates to loop filesystem ('cvs up; emerge metadata' or 'emerge > sync') 5. umount loop file, copy back to disk > 6. mount loop file again Since (from what I've heard) Portage's speed issues are mostly I/O, why not= =20 keep the mounted copy on a tmpfs and simply make an on-disk backup after=20 syncing (and copy it back on rebooting)? On Thursday 14 October 2004 2:07 pm, Ned Ludd wrote: > New loopback size is 11M after reading this thread and dumping ChangeLog > & metadata.xml files which does seem like a perfectly feasible thing for > us to do. Removing leading/trailing whitespace and erroneous newlines > yielded no noticeable gains. 11 MB of RAM may or may not seem reasonable to users depending on how often= =20 they do things with Portage. =2D-=20 Luke-Jr Developer, Utopios http://utopios.org/ --nextPart1553956.AjqLMcc6OV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQBBbqhLZl/BHdU+lYMRAt2sAJ0QUtqXJ7SmzA1Z5FvpPYshDSTu7ACdFMSI Sharlq5pPfPAFQSceNlw/U0= =YgTF -----END PGP SIGNATURE----- --nextPart1553956.AjqLMcc6OV--