From: "Chris Bainbridge" <chris.bainbridge@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] overlay support current proposal?
Date: Mon, 27 Mar 2006 09:51:43 +0100 [thread overview]
Message-ID: <623652d50603270051l2636dd32g48af486fa4705f2e@mail.gmail.com> (raw)
In-Reply-To: <20060327054353.GA9018@trolocsis.dyndns.org>
On 27/03/06, Ryan Phillips <rphillips@gentoo.org> wrote:
> Aron Griffis <agriffis@gentoo.org> said:
> > Have you followed the threads in the past regarding using other
> > version control systems for portage? Some devs have done benchmarks
> > and found that there are blocking issues with subversion, particularly
> > because of its repo-wide revisions that prevent multiple commits from
> > happening simultaneously.
>
> In actuality, Subversion does 98% of the commit in an initial
> transaction, and the blocking only occurs in the last 2% with the FSFS
> filesystem. It really isn't an issue and shouldn't prevent us from
> adopting it.
All svn commits are atomic, and that requires some kind of global
lock. I'd say the (slight) performance penalty is worth it for that
feature alone. I'd also point out that the KDE project have everything
in a single svn repository and can manage >10,000 commits per month
with no problems. There are various testimonials around from people
claiming to be running svn on multiple GB repositories with >17,000
commits a month.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-27 8:54 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 19:35 [gentoo-dev] overlay support current proposal? Grant Goodyear
2006-03-24 19:54 ` Aron Griffis
2006-03-24 20:06 ` Daniel Ostrow
2006-03-24 20:13 ` Daniel Ostrow
2006-03-24 20:44 ` Stuart Herbert
2006-03-25 0:34 ` Alec Warner
2006-03-25 2:31 ` Diego 'Flameeyes' Pettenò
2006-03-25 11:41 ` Duncan Coutts
2006-03-25 11:49 ` Diego 'Flameeyes' Pettenò
2006-03-25 15:08 ` Carsten Lohrke
2006-03-25 18:50 ` Diego 'Flameeyes' Pettenò
2006-03-25 20:36 ` Carsten Lohrke
2006-03-25 22:17 ` Stephen P. Becker
2006-03-25 11:42 ` Kevin F. Quinn (Gentoo)
2006-03-25 11:46 ` Duncan Coutts
2006-03-25 12:32 ` Kevin F. Quinn (Gentoo)
2006-03-25 12:37 ` Duncan Coutts
2006-03-25 13:28 ` Kevin F. Quinn (Gentoo)
2006-03-25 11:47 ` Diego 'Flameeyes' Pettenò
2006-03-25 6:47 ` Ryan Phillips
2006-03-25 11:55 ` [gentoo-dev] " Duncan
2006-03-25 23:00 ` [gentoo-dev] " Aron Griffis
2006-03-25 23:12 ` Aron Griffis
2006-03-25 23:20 ` Fernando J. Pereda
2006-03-25 23:18 ` Fernando J. Pereda
2006-03-26 0:57 ` Aron Griffis
2006-03-26 9:54 ` Fernando J. Pereda
2006-03-26 20:28 ` Greg KH
2006-03-27 5:43 ` Ryan Phillips
2006-03-27 8:29 ` Paul de Vrieze
2006-03-27 20:58 ` Dan Armak
2006-03-28 9:25 ` Paul de Vrieze
2006-03-27 8:51 ` Chris Bainbridge [this message]
2006-03-27 14:15 ` Chris Gianelloni
2006-03-26 1:30 ` Duncan Coutts
2006-03-26 4:39 ` Luca Barbato
2006-03-26 9:57 ` Fernando J. Pereda
2006-03-28 16:29 ` Patrick McLean
2006-03-30 12:40 ` Stuart Herbert
2006-03-30 18:54 ` Aron Griffis
2006-03-31 8:16 ` Stuart Herbert
2006-03-31 8:24 ` Fernando J. Pereda
2006-03-31 11:36 ` Duncan Coutts
2006-03-30 14:08 ` Nguyễn Thái Ngọc Duy
2006-03-25 10:16 ` Luca Barbato
2006-03-25 23:04 ` Aron Griffis
2006-03-25 23:32 ` Luca Barbato
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=623652d50603270051l2636dd32g48af486fa4705f2e@mail.gmail.com \
--to=chris.bainbridge@gmail.com \
--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