On Wed, 2005-11-23 at 09:39 +0100, Arnaud Charlet wrote: > > Most svn side operations create subpools for loops that may allocate > > per-iteration memory due to calls to other functions, etc, and clear it > > each iteration to avoid such per iteration allocations become too large. > > Some don't. > > FWIW, the first (and only) time I tried to do a svn diff on lots of > files (about 700), svn diff never returned: my machine started to swap > and be unresponsive like hell, and I had a very hard time hitting ^C > to stop it.
Uh, i've never seen such behavior from *SVN*. SVN diff requires stat'ing a lot of files currently (and in 1.2.3, opening and reading a bunch of almost-empty files), but *memory usage* should be close to nothing. It'd be really nice if you could reproduce this behavior so i can fix it. --Dan
