public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] DVCS update
Date: Tue, 10 Feb 2009 14:08:26 -0800	[thread overview]
Message-ID: <20090210220826.GB32706@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <20090210215134.GE3692@comet>

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

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@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 329 bytes --]

  reply	other threads:[~2009-02-10 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 21:51 [gentoo-council] DVCS update Donnie Berkholz
2009-02-10 22:08 ` Robin H. Johnson [this message]
2009-02-10 23:06   ` Donnie Berkholz
2009-02-11 13:30 ` Luca Barbato
2009-02-11 19:19   ` Donnie Berkholz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090210220826.GB32706@curie-int.orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox