Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-council
Navigation:
Lists: gentoo-council: < Prev By Thread Next > < Prev By Date Next >
Headers:
From: "Robin H. Johnson" <robbat2@g.o>
Subject: Re: DVCS update
Date: Tue, 10 Feb 2009 14:08:26 -0800
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 
> resources are required. I've talked to a number of git admins 
> (kernel.org, fedora, freedesktop.org, gnome), and they have all said the 
> hardware requirements for git are negligible. They don't have any 
> resource on their servers that's being used up. It's gitweb that is 
> 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.

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.

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail     : robbat2@g.o
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85
Attachment:
pgpwSJkfud4ND.pgp (PGP signature)
Replies:
Re: DVCS update
-- Donnie Berkholz
References:
DVCS update
-- Donnie Berkholz
Navigation:
Lists: gentoo-council: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
DVCS update
Next by thread:
Re: DVCS update
Previous by date:
DVCS update
Next by date:
Re: DVCS update


Updated Jun 17, 2009

Summary: Archive of the gentoo-council mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.