From: Larry McVoy <lm@bitmover.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Walter Landry <wlandry@ucsd.edu>, linux-kernel@vger.kernel.org
Subject: Re: A simple request (was Re: boring BK stats)
Date: Thu, 10 Oct 2002 07:28:18 -0700 [thread overview]
Message-ID: <20021010072818.F27122@work.bitmover.com> (raw)
In-Reply-To: <3DA58B60.1010101@pobox.com>; from jgarzik@pobox.com on Thu, Oct 10, 2002 at 10:14:56AM -0400
> 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
> that is impossible to optimize at the SCM level without compromising
> features... if your source tree takes up ~190MB on disk, you have 200MB
> of RAM total, and you need to sequentially scan the entire thing, there
> is nothing that can be done at either the OS or app level... You're just
> screwed. Things are extremely fast on the Dual Athlon because the
> entire tree is in RAM.
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.
For the checkouts, always do a "bk -r get -S" the -S doesn't check out the
file again if it is already there. We could make that the default but
it is an interface change. A fairly minor one though.
We've got some other fixes in the pipeline for the checkin and integrity
check pass.
There is only so much we can do when you are trying to cram 10 pounds of
crap in a 5 pound bag :(
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-10-10 14:22 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 [this message]
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
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=20021010072818.F27122@work.bitmover.com \
--to=lm@bitmover.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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