From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Larry McVoy <lm@work.bitmover.com>,
Jeff Garzik <jgarzik@pobox.com>, Walter Landry <wlandry@ucsd.edu>,
linux-kernel@vger.kernel.org
Subject: Re: A simple request (was Re: boring BK stats)
Date: Fri, 11 Oct 2002 16:08:28 +0200 [thread overview]
Message-ID: <20021011160828.B345@bitwizard.nl> (raw)
In-Reply-To: <20021011153538.A345@bitwizard.nl>
On Fri, Oct 11, 2002 at 03:35:38PM +0200, Rogier Wolff wrote:
> On Thu, Oct 10, 2002 at 07:28:18AM -0700, Larry McVoy wrote:
> > > The laptop has 200MB RAM, and mozilla and a ton of xterms loaded. IDE
> > > drives w/ Intel PIIX4 controller. The Dual Athlon has 512MB RAM, and I
> > > forget what kind of IDE controller -- I think AMD. IDE drives as well.
> > >
> > > BitKeeper must scan the entire tree when doing a checkin or checkout, so
>
> [...]
>
> > In low memory situations you really want to run the tree compressed.
> > ON a fast machine do a "bk -r admin -Z" and then clone that onto your
> > laptop. I think that will drop the tree to about 145MB which will
> > help, maybe. I suspect that you use enough of the rest of your 200MB
> > that it still won't fit.
>
> [...]
> > There is only so much we can do when you are trying to cram 10 pounds of
> > crap in a 5 pound bag :(
>
> The reason that one or two years ago my "diff+multiple trees" beat
> bitkeeper on the performance front was that diff would only touch
> inode-metadata, and not the files themselves. You can cache the
> file-metadata (inodes) of a 200M tree in a couple of megabytes of RAM.
Jeff:
The trick is that I would have hardlinked trees. Thus
linux-2.2.18.clean/drivers/char/tty_ioctl.c
and
linux-2.2.18.rio/drivers/char/tty_ioctl.c
would have the same inode number, and diff wouldn't even bother to
open the file....
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* The Worlds Ecosystem is a stable system. Stable systems may experience *
* excursions from the stable situation. We are currenly in such an *
* excursion: The stable situation does not include humans. ***************
next prev parent reply other threads:[~2002-10-11 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 23:39 A simple request (was Re: boring BK stats) Walter Landry
2002-10-10 14:14 ` Jeff Garzik
2002-10-10 14:28 ` Larry McVoy
2002-10-10 14:40 ` Jeff Garzik
2002-10-10 15:32 ` Theodore Ts'o
2002-10-11 13:35 ` Rogier Wolff
2002-10-11 14:08 ` Rogier Wolff [this message]
2002-10-11 14:14 ` Rogier Wolff
2002-10-10 22:51 ` A simple request Walter Landry
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=20021011160828.B345@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=wlandry@ucsd.edu \
/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