From: Yuri Mikhailov <yuri.mikhaylov@gmail.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: thomas@koch.ro, git <git@vger.kernel.org>
Subject: Re: Load testing of git
Date: Tue, 5 Mar 2013 23:04:28 +0100 [thread overview]
Message-ID: <CAGjB8pT-HCDY-M7nP_YCGyyvAtVZnMYynm7rVypp66Ve2g-azA@mail.gmail.com> (raw)
In-Reply-To: <CAJo=hJvX5rmsuB4Jsbp7ZoqeyPtB_fwiZc=8VMWmF=HN0XKGLw@mail.gmail.com>
Thanks to everyone. The information was useful.
On 24 February 2013 21:31, Shawn Pearce <spearce@spearce.org> wrote:
> On Sun, Feb 24, 2013 at 8:58 AM, Thomas Koch <thomas@koch.ro> wrote:
>> Yuri Mikhailov:
>>> Dear Git community,
>>>
>>> I am a Software Developer and I have been using git for a while.
>>> Currently my company is looking for a version control system to use
>>> and we find Git a good candidate for us. But what is important for us
>>> to know is scalability of this VCS. Does anyone performed load testing
>>> of Git? What is the practical maximum number of files and revisions
>>> this system can handle?
>>>
>>> Best regards,
>>> Iurii Mykhailov
>>
>> Have a look at the projects using Git[1]. There are for sure projects that
>> exceeds the scalability you're thinking about. The linux Kernel might be the
>> biggest project.
>
> I highly doubt the Linux kernel is the biggest project.
>
> IIRC WebKit has more objects, more files, etc. Its repository's
> compressed form is >4G.
>
> I know of at least some proprietary repositories with 96G in them. Not
> much history, but a lot of binary blobs around 128M each doesn't
> compress well. And bup wasn't used so we didn't get very good
> compression over the files.
next prev parent reply other threads:[~2013-03-05 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 12:54 Load testing of git Yuri Mikhailov
2013-02-24 16:58 ` Thomas Koch
2013-02-24 20:31 ` Shawn Pearce
2013-03-05 22:04 ` Yuri Mikhailov [this message]
2013-02-24 17:54 ` Jeff Epler
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=CAGjB8pT-HCDY-M7nP_YCGyyvAtVZnMYynm7rVypp66Ve2g-azA@mail.gmail.com \
--to=yuri.mikhaylov@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=thomas@koch.ro \
/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;
as well as URLs for NNTP newsgroup(s).