RE: Re: Big memory use after update

It happened on a commit, didn't it? So perhaps a dump/reload of that entire
repository might trigger it on re-committing that revision?
Is it possible to reload a repository up to the point before that commit
that triggered this problem, and then the revision that contained this
commit somehow have it applied as a patch against a working copy, then
commit that over http?

regards,

--Tim

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: vrijdag 28 november 2003 16:03
To: Juanma Barranquero
Cc: Sander Striker; users@subversion.tigris.org
Subject: Re: Big memory use after update

On Fri, 2003-11-28 at 06:53, Juanma Barranquero wrote:

> But I do svn update a lot of times and the memory doesn't grow. So
> *something* happened this one time. I'm sorry I don't have more accurate
> information.

It's frustrating, since we just spent the last two months fixing memory
scalability bugs, and nobody can come up with a reliable reproduction
recipe for this. We thought it was a win32-only glitch, but it seems
that's not even true.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 1 11:59:23 2003