random thought of the day - a progress bar for tree transforms ?

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A Meinel wrote:
> Aaron Bentley wrote:
> 
>>Robert Collins wrote:
>>| Aaron,
>>|     you may have done this already, but what do you think of the idea of
>>| tree transform operations accepting a progress bar?
>>
>>Yeah, we could do that.  Off the top of my head, there are four phases:
>>1. transform creation (calculating the build, revert or merge operation)
>>2. resolution of filesystem conflicts (this may run 1 to 10 times)
>>3. application of removals (renames, deletions, unversioning)
>>4. application of insertions (renames, creations, versioning)
>>
>>I suspect that your average transform spends most of its time in 2.
>>
>>Aaron
> 
> 
> How do you get '1-10' times?

Conflict resolution may introduce new conflicts.  Rather than try to
predict all the possible interactions, I thought it would be more robust
to just run the resolver several times.  10 seemed like a good number.

> It just realizes that it could conflict
> that many times? Or are you just saying "this could run repeatedly".

10 is the maximum.

> It would be really nice to have transform have a progress bar, since in
> a pull you tend to get a progress, and then all goes silent for quite
> some time.

Okay, I can do that, but I'll do it in a separate branch, so it doesn't
interfere with getting Transform merged.

> I'm thinking that if it is a fixed number of iterations, just do the
> progress as 14 steps, and skip ones you don't use.
> But it might be nicer to have an idea how many files you are checking,
> and iterate over that instead.

On the plus side, we all seem to agree that nested progress bars would
be nice.  On the minus side, no one's actually done it yet...

> (That, and we need to figure out why branch doesn't do anything for
> quite some time, it doesn't seem to be CPU or bandwidth bound during
> that time, probably latency bound).

I dunno.  For merge, I'd have a guess, but not for branch.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD8gvv0F+nu1YWqI0RAjKjAJ4hbmy7tY08SL2xG91lAPX1u5pfPACcD/dJ
KT0IBeXsR+yUFUxGXcwyVHI=
=7vlk
-----END PGP SIGNATURE-----