From: Stan Bubrouski <stan@ccs.neu.edu>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: davidm@hpl.hp.com, akpm@osdl.org,
Andreas Hirstius <Andreas.Hirstius@cern.ch>,
Bartlomiej ZOLNIERKIEWICZ <Bartlomiej.Zolnierkiewicz@cern.ch>,
Gelato technical <gelato-technical@gelato.unsw.edu.au>,
linux-kernel@vger.kernel.org
Subject: Re: [Gelato-technical] Re: Serious performance degradation on a RAID with kernel 2.6.10-bk7 and later
Date: Thu, 21 Apr 2005 14:24:52 -0400 [thread overview]
Message-ID: <4267EFF4.1000307@ccs.neu.edu> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F0350B3F4@scsmsx401.amr.corp.intel.com>
Luck, Tony wrote:
>>Yeah, I'm facing the same issue. I started playing with git last
>>night. Apart from disk-space usage, it's very nice, though I really
>>hope someone puts together a web-interface on top of git soon so we
>>can seek what changed when and by whom.
>
>
> Disk space issues? A complete git repository of the Linux kernel with
> all changesets back to 2.4.0 takes just over 3G ... which is big compared
> to BK, but 3G of disk only costs about $1 (for IDE ... if you want 15K rpm
> SCSI, then you'll pay a lot more). Network bandwidth is likely to be a
> bigger problem.
>
That said, is there any plan to change how this functions in the future
to solve these problems? I.e. have it not use so much diskspace and
thus use less bandwith. Am I misunderstanding in assuming that after
say 1000 commits go into the tree it could end up several megs or gigs
bigger?
If that is the case might it not be more prudent to sort this out now?
> There's a prototype web i/f at http://grmso.net:8090/ that's already looking
> fairly slick.
>
Yes it is very slick. Kudos to the creator.
-sb
> -Tony
next prev parent reply other threads:[~2005-04-21 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 17:41 [Gelato-technical] Re: Serious performance degradation on a RAID with kernel 2.6.10-bk7 and later Luck, Tony
2005-04-21 17:48 ` David Mosberger
2005-04-21 18:24 ` Stan Bubrouski [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 18:29 Luck, Tony
2005-04-21 18:40 ` Stan Bubrouski
2005-04-21 17:19 Luck, Tony
2005-04-21 17:33 ` David Mosberger
2005-04-21 17:39 ` Randy.Dunlap
2005-04-20 17:37 Andreas Hirstius
2005-04-20 16:55 ` jmerkey
2005-04-21 8:32 ` Andreas Hirstius
[not found] ` <58cb370e05042102272ce70f2@mail.gmail.com>
2005-04-21 9:42 ` Bartlomiej ZOLNIERKIEWICZ
2005-04-21 11:30 ` Andreas Hirstius
2005-04-21 15:05 ` [Gelato-technical] " David Mosberger
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=4267EFF4.1000307@ccs.neu.edu \
--to=stan@ccs.neu.edu \
--cc=Andreas.Hirstius@cern.ch \
--cc=Bartlomiej.Zolnierkiewicz@cern.ch \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=gelato-technical@gelato.unsw.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/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