[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: import problems (mostly) fixed

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2002-03-08 00:42:45 CET

On Thu, Mar 07, 2002 at 04:53:45PM -0600, Ben Collins-Sussman wrote:
>
> So M10 has been working towards killing the last "showstopper" memory
> bug... namely the inability to import a massive tree (such as when
> BenC tries to import the linux kernel... he runs out of swap!)
>
> Here's my original test case:
>
> Importing emacs source tree: 86 megs, 3000 files & dirs.
>
> * import: 290 megs of RAM used. (sending inline txdeltas)
>
> * add/commit: 108 megs of RAM used, then stayed there as postfix
> txdeltas were sent.
>
> It -seems- that the problem was that there were simply too many pools
> being created and held around. Remember that each pool, when created,
> is a *minimum* of 8K. Gstein's latest commit (r1456) has drastically
> reduced the number of these pools.
>
> As a result, my import now uses only 16 megs.
>
> In general, something is still vaguely wrong; even 16 megs is too
> high. But this is generally passable for M10, which we'll start
> rolling tomorrow.
>
> Ben Collins: you might want to try re-doing your linux kernel import
> and see what you get.

Well, I'm not Ben Collins, but as of revision 1458, i can now Import
the FreeBSD-STABLE src/sys tree and memory usage doesn't climb about
about 40 megs. This seems much more reasonable than what people were
reporting before.

-garrett

-- 
garrett rooney                     Unix was not designed to stop you from 
rooneg@electricjellyfish.net       doing stupid things, because that would  
http://electricjellyfish.net/      stop you from doing clever things.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 8 00:43:17 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.