Jeff Garzik wrote:
> If you can't fit a whole tree including metadata into RAM, though,
> BK crawls... Going from "bk citool" at the command line to actually
> seeing the citool window approaches five minutes of runtime, on this
> 200MB laptop... [my dual athlon with 512MB RAM corroborates your
> numbers, though] "bk -r co -Sq" takes a similar amount of time...
>
> I also find that BK brings out the worst in the 2.4 kernel
> elevator/VM... mouse clicks in Mozilla take upwards of 10 seconds to
> respond, when "bk -r co -Sq" is running on this laptop [any other
> read-from-disk process behaves similarly]. And running any two BK
> jobs at the same time is a huge mistake. Two "bk -r co -Sq" runs
> easily take four or more times longer than a single run. Ditto for
> consistency checks, or any other disk-intensive activity BK indulges
> in.
Hello,
What kind of CPU and hard drive do your two machines above have? I'm
a developer for arch[1], and I'm wondering how fast things can get.
Note: If you answer, you'll certainly be aiding arch development. It
might be interpreted as "develop[ing] ... a product which
contains substantially similar capabilities of the BitKeeper
Software, or, in the reasonable opinion of BitMover, competes
with the BitKeeper Software". So you might lose the ability to
use the free license. But I'll let you decide if you want to
help us.
Thank you,
Walter Landry
wlandry@ucsd.edu
[1] www.fifthvision.net/Arch
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:34 EST