From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LX1gi-0003Vj-5j for garchives@archives.gentoo.org; Tue, 10 Feb 2009 23:06:44 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8C48AE04F1; Tue, 10 Feb 2009 23:06:43 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 6C18CE04F1 for ; Tue, 10 Feb 2009 23:06:43 +0000 (UTC) Received: from gentoo.org (xray.science.oregonstate.edu [128.193.220.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 1A248663D6; Tue, 10 Feb 2009 23:06:43 +0000 (UTC) Date: Tue, 10 Feb 2009 15:06:42 -0800 From: Donnie Berkholz To: "Robin H. Johnson" Cc: gentoo-council@lists.gentoo.org Subject: Re: [gentoo-council] DVCS update Message-ID: <20090210230642.GF3692@comet> References: <20090210215134.GE3692@comet> <20090210220826.GB32706@curie-int.orbis-terrarum.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-council@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tmoQ0UElFV5VgXgH" Content-Disposition: inline In-Reply-To: <20090210220826.GB32706@curie-int.orbis-terrarum.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-Archives-Salt: 8dd4691b-a7de-4b22-ac2b-753cba4c91bc X-Archives-Hash: 942cdc671c367edfb69d6b86b66229d2 --tmoQ0UElFV5VgXgH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 14:08 Tue 10 Feb , Robin H. Johnson wrote: > On Tue, Feb 10, 2009 at 01:51:34PM -0800, Donnie Berkholz wrote: > > - Robin has commented that he doesn't know what kind of server-side=20 > > resources are required. I've talked to a number of git admins=20 > > (kernel.org, fedora, freedesktop.org, gnome), and they have all said th= e=20 > > hardware requirements for git are negligible. They don't have any=20 > > resource on their servers that's being used up. It's gitweb that is=20 > > somewhat resource-intensive. > > A specific comment on this (I know I've been away lately, I'm busy > getting back to things now that I've moved house). Git devours RAM. > During pull actions, if the pull triggers a build of a custom pack on > the server, it can snowball to kill the box with IO load due to swap and > later OOM. >=20 > The git-upload-pack that runs on the server side when you do a 'git > clone ...' at the moment for the gentoo-x86.git repo exceeds 1GB of RAM > after 10 minutes of running. The box only has 2GB of RAM, so it hits > swap quickly, and things go downhill very fast from there. Thanks, Robin! To be very specific about one of the above, the Gnome box=20 is a dual-CPU with 8G RAM on some kind of RAID. Owen Taylor (otaylor on=20 IRC) informed me that it handled git with no problem at insignicant=20 load. OTOH, I don't know of anyone with a repo more than 1/2 the size of ours=20 and maybe 1/4 the object count. My local clone of the kernel is ~600M. --=20 Thanks, Donnie Donnie Berkholz Developer, Gentoo Linux Blog: http://dberkholz.wordpress.com --tmoQ0UElFV5VgXgH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkmSCIIACgkQXVaO67S1rtsFwACfUBc96ToJi1UjaLucWjcsu4WL U0EAnAt3rqkyJMAbRN6pgU9q6B23T4Ax =Izml -----END PGP SIGNATURE----- --tmoQ0UElFV5VgXgH--