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

Re: Providing accurate progress information during operations

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-07-15 08:55:23 CEST

steveking <steveking@gmx.ch> writes:

> Greg Hudson wrote:
> > On Thu, 2005-07-14 at 16:34 -0400, Mark Phippard wrote:
> >
> >> What we would probably need is some kind of notifcation up front
> >> that tells us we are going to receive 57 files or 568 kB, or
> >> something like that.
> > In order to compute this number, we'd have to do a significant
> > amount of
> > work up front which we currently defer.
> > That is, we'd get more precise progress notifications, but only at
> > the
> > expense of spending a longer time up front with no progress
> > notifications.
> Are you sure about this? I mean Subversion already knows (at least
> when *sending* changes to the repository) what the changes are before
> sending them.

All Greg was saying is that even when sending changes to the server,
Subversion doesn't know the total size of the dataset at the start of
the 'svn commit' operation or within an user-unnoticeable amount of
time after the start of that operation, as it could take significantly
long to crawl the working copy looking for changes.

I'll add that even after the crawl it doesn't know the size of the
transmission, because while some stat() calls across the files in the
committables list would reveal the size of those files, the size of
the delta transmitted for each file is another matter completely. I
find progress meters that appear to be showing linear progress across
a workset but in fact update "jumpily" and misproportionally to be

> And it might help a lot if just the number of bytes already
> transferred could be shown (so the user know that *something* is going
> on), even if the total amount isn't known.

I can see that being at least somewhat useful, but would again suffer
the same delay while committables are harvested, and again during
post-commit operations.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 08:58:08 2005

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.