From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: proxy maintainership and gentoo-x86 scm
Date: Fri, 15 Jan 2010 00:47:57 +0000 [thread overview]
Message-ID: <20100115004757.GG16921@orbis-terrarum.net> (raw)
In-Reply-To: <slrnhkvcd5.623.flowerysong00@shasta.marwnad.com>
[-- Attachment #1: Type: text/plain, Size: 2132 bytes --]
On Thu, Jan 14, 2010 at 07:07:01PM -0500, Paul Arthur wrote:
> On 2010-01-14, Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> > On Wed, Jan 13, 2010 at 9:24 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> >> i think our current work flows also significantly impede the smooth running of
> >> this. Â if we had were using a dscm (git) on gentoo-x86, i feel like it'd be a
> >> much smoother ride for Gentoo devs to pull from a proxy maintainer and push on
> >> their behalf.
> >
> > In theory, yes. In practice, git is too slow to handle 30,000 files.
> > Even simple operations like git add become painful even if you put the
> > whole of portage on tmpfs since git does a stat() on every single file
> > in the repository with every operation.
> >
> > Simple test: do a git init followed by git add && git commit -m
> > "Initial commit" in your portage dir (.gitignore packages/ and
> > distfiles/)
> >
> > Once this is done, you can test how it'll feel like to use a DSCM on
> > portage (without history). Unless you have a really fast SSD and
> > processor, you'll want to go back to the good old days of CVS with its
> > network-bound latencies on just 5-6 files in the current dir.
>
> Ouch. I wanted to test this in a fairly bad scenario, so I gave it a
> try on my old, low-spec fileserver.
You didn't repack or at least run git-gc between the huge add and your
everyday operations. Do that, and then measure the ops with both cold
and hot cache.
The initial packing and adding are very intensive, even on fast
machines, but that's because they are dealing with a lot of small pieces
of data. Packing has benefited immensely from being fully multi-threaded
in Git.
I'd love somebody to do the SoC stats again:
http://www.gentoo.org/proj/en/infrastructure/cvs-migration.xml?style=printable
Using the git repo conversion I did:
http://git-exp.overlays.gentoo.org/gitweb/?p=exp/gentoo-x86.git;a=summary
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 330 bytes --]
next prev parent reply other threads:[~2010-01-15 0:48 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 21:05 [gentoo-dev] Last rites: net-nntp/inn Markos Chandras
2010-01-11 22:31 ` Mike Frysinger
2010-01-12 1:00 ` Jeroen Roovers
2010-01-12 20:31 ` Mike Frysinger
2010-01-11 23:30 ` [gentoo-dev] " Arnaud Launay
2010-01-12 1:02 ` Jeroen Roovers
2010-01-12 2:22 ` Jeroen Roovers
2010-01-12 5:03 ` [gentoo-dev] Thanks for the rescue! Was: " Duncan
2010-01-12 16:32 ` [gentoo-dev] " Markos Chandras
2010-01-12 18:21 ` Jeroen Roovers
2010-01-12 18:30 ` Markos Chandras
2010-01-12 19:07 ` Richard Freeman
2010-01-12 22:37 ` Duncan
2010-01-13 1:18 ` Arnaud Launay
2010-01-13 5:52 ` Jeroen Roovers
2010-01-13 15:06 ` Arnaud Launay
2010-01-13 16:31 ` Richard Freeman
2010-01-13 5:48 ` Jeroen Roovers
2010-01-13 8:05 ` Duncan
2010-01-12 19:40 ` Arnaud Launay
2010-01-12 19:49 ` Markos Chandras
2010-01-12 20:35 ` Ben de Groot
2010-01-12 22:24 ` Duncan
2010-01-13 15:54 ` [gentoo-dev] proxy maintainership and gentoo-x86 scm Mike Frysinger
2010-01-13 21:02 ` Ben de Groot
2010-01-13 21:18 ` justin
2010-01-13 22:03 ` [gentoo-dev] " Christian Faulhammer
2010-01-14 13:30 ` [gentoo-dev] " Markos Chandras
2010-01-14 16:35 ` Ben de Groot
2010-01-14 12:49 ` Nirbheek Chauhan
2010-01-14 13:47 ` Nguyen Thai Ngoc Duy
2010-01-14 22:10 ` Nirbheek Chauhan
2010-01-15 13:17 ` Nguyen Thai Ngoc Duy
2010-01-14 16:24 ` Ben de Groot
2010-01-14 17:04 ` "Paweł Hajdan, Jr."
2010-01-14 19:46 ` Pacho Ramos
2010-01-14 22:53 ` Nirbheek Chauhan
2010-01-14 20:31 ` Daniel Bradshaw
2010-01-14 22:21 ` Nirbheek Chauhan
2010-01-14 22:29 ` Nirbheek Chauhan
2010-01-14 22:54 ` Robin H. Johnson
2010-01-14 23:25 ` Petteri Räty
2010-01-15 8:32 ` Mike Frysinger
2010-01-14 23:28 ` Nirbheek Chauhan
2010-01-19 22:29 ` Arun Raghavan
2010-01-14 22:32 ` Daniel Bradshaw
2010-01-15 0:07 ` [gentoo-dev] " Paul Arthur
2010-01-15 0:47 ` Robin H. Johnson [this message]
2010-01-15 7:53 ` [gentoo-dev] " Max Arnold
2010-01-15 15:50 ` [gentoo-dev] Re: Last rites: net-nntp/inn Victor Ostorga
2010-01-15 16:09 ` Ben de Groot
2010-01-17 20:20 ` Thilo Bangert
2010-01-17 20:44 ` Richard Freeman
2010-01-17 21:12 ` Mike Frysinger
2010-01-17 22:25 ` Thilo Bangert
2010-01-18 1:23 ` Ben de Groot
2010-01-18 2:17 ` Richard Freeman
2010-01-20 13:49 ` Petteri Räty
2010-01-12 1:10 ` Duncan
2010-01-12 1:36 ` Richard Freeman
2010-01-12 3:43 ` Jeremy Olexa
2010-01-12 18:01 ` Richard Freeman
2010-01-12 20:33 ` Mike Frysinger
2010-01-12 20:51 ` Tomáš Chvátal
2010-01-12 21:39 ` Denis Dupeyron
2010-01-13 5:45 ` Jeroen Roovers
2010-01-13 14:24 ` Mike Frysinger
2010-01-13 16:27 ` Richard Freeman
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=20100115004757.GG16921@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@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