What would it take to reduce/remove the sleeps all the time?
Just the other day I needed to build up a directory structure for testing.
I wrapped up a quick script that did "svn mkdir http://..." for each one
(this is over WebDAV). The performance was horrible! Each one took 2-3
The point is that many simple operations are sluggish because of this "wait
for next second" stuff. The sleep dominates the transaction time and make
svn appear much slower than it could be. I'm trying to sell this to me
team, but I have to dance around the fact that some simple operations seem
to be really slow (while "hard" things like "diff" are quite fast).
Can we kill the sleeps without losing correctness?
I've got CPU and memory to spare, but I can never get back the time.
P.S. Yes, there are other ways to do this that would be faster. That's not
the point. I actually rewrote the script twice while waiting for the
original implementation to finish. That kind of "gotcha" doesn't help me
P.P.S. I also don't know why it is doing the sleep when there is no WC
involved. I'm guessing it is following the same code path for both the pure
URL case and the WC case.
On 3/11/07, Erik Huelsmann <firstname.lastname@example.org> wrote:
> In the last few days, I committed an extra criterion to help determine
> 'changedness' of a file: libsvn_wc also considers the size of the file
> at hand. So, now we do not only depend on the timestamp any more. If a
> file changes in size (but not in time), svn will detect it's possibly
Received on Mon Mar 12 17:40:37 2007