GUI Option to set zsync as default

Bug #701818 reported by Vish
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
TestDrive
Triaged
Low
Unassigned
testdrive (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: testdrive

There doesnt seem to be any way to set zsync as the default method to sync the iso. (http://askubuntu.com/questions/15893/how-to-force-testdrive-to-use-zsync/21089#21089)

I have tried updating the Ubuntu iso with testdrive and with using zsync alone and i find zsync uses lesser data to update the iso.
I'm doubtful is because: every-time I use testdrive, for a 2day old iso, the whole iso(700mb) is downloaded again. It starts from 0% .
But when I use zsync($ zsync -i ~/Downloads/natty-desktop-i386.iso http://cdimage.ubuntu.com/daily-live/current/natty-desktop-i386.iso.zsync) it starts from 50% or 60% even when the iso is 1week to 10days old. (I have no specific debugging info but this is just from the behavior I'v noticed.)

It would be great if I could use zsync as the default method for testdrive instead of rsync.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: testdrive (not installed)
ProcVersionSignature: Ubuntu 2.6.32-27.48~lp652934v201011301338-generic 2.6.32.26+drm33.11
Uname: Linux 2.6.32-27-generic i686
Architecture: i386
Date: Wed Jan 12 11:15:09 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100924)
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: testdrive

Vish (vish)
Changed in testdrive (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi Vish,

Thank you for reporting bugs. I do have a few questions though:

When using rsync, do you mean that it starts from 0% in the GUI?
How do you know it actually downloads the whole ISO (700mb) instead of only what has changed? How have you tested this?

I'm asking this because when downloading a, i.e. 2 day old ISO, the percentage that TestDrive GUI shows will always start from 0, to 100, regardless of whether it is downloading ~100mb, ~200mb, etc, or the ~700mb of a complete ISO. If you wanna see the different, you might wanna do the following:

1. System > Administration > System Monitor
2. Under Network History, check Total Received.
3. Start syncing an ISO that's 2 days old. Wait for it to finish and see the "Total Received" filed mentioned above.
4. To compare, do the same with an ISO that's not been previously downloaded. You will then see the difference.

However, I'll consider giving the option to select zsync as an alternate sync method in the future.

Best regards.

Changed in testdrive (Ubuntu):
status: New → Triaged
Changed in testdrive:
status: New → Triaged
importance: Undecided → Low
Changed in testdrive (Ubuntu):
importance: Wishlist → Low
Revision history for this message
Vish (vish) wrote :

Even before the GUI was available, why i thought it re-downloaded the whole 700mb each time was since i notice :
a file ~/.cache/testdrive/iso/.ubuntu_natty-desktop-i386.iso.k2uD6e (the last "k2uD6e" is random as you would already know) gets created first with 0 bytes everytime(i have nautilus configured to display the filesize)
 and then once it reaches 700mb it overwrites/replaces the ~/.cache/testdrive/iso/ubuntu_natty-desktop-i386.iso
And it takes(or seems to) a lot longer than zsync. I dont recall seeing it update the iso quickly.

However, since these are not really accurate measurements, I'm updating the iso again today and I will be checking with sysmonitor how it goes with both the zsync/testdrive(rsync?) and will file a separate bug with info.

Revision history for this message
Vish (vish) wrote :

Bah!! I was completely wrong.. (unless you guys secretly, magically updated testdrive with no version updates ;p )

The download amount does not match the ~700mb. The amount that had been downloaded was lesser .
I seem to have been mislead by how the two work differently.
Testdrive starting at 0% and the file size count starting at 0 is a bit confusing.
The reason this is misleading is, because, 0% --> 100% time will *never* be the same. Since it seems to be secretly syncing and then recording the percent complete of the file.

But it might be better if testdrive gave the actually amount of sync progress. (like how we notice in zsync.)
 This would give us a better estimate of the time left to sync rather than a sync which takes random amount of time.
Is this a limitation of rsync? And would it be fixed when we have this zsync option ?
Or should i file a separate bug requesting better sync progress reporting?

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Vish,

Indeed the starting at 0% might have been misleading but unfortunately this is given by rsync itself. The thing is that when rsync starts "updating" and ISO, it starts from 0 to XX (in let's say 10 seconds), where XX will be the percentage that is already downloaded, from that point, it will start moving from XX to 100% (in the time it takes to download that percentage left).

Because of this, it *seems* that rsync is downloading a new ISO completely when it is not. It is just updating the ISO. For this reason it is why testdrive will always show from 0 to 100%.

And yes, this is a limitation from rsync, and to tell you the truth, using *zsync* causes the progress to change depending on what step it is downloading, and it is not always accurate. But you can still use *zsync* though.

To do this, just do to the "Other" tab, and click on "Add ISO" and in the new dialog, add the URL of the ISO you wan't to download and select zsync as downloading protocol

Either way, I personally prefer rsync. You don't need to file another bug!

Best regards,

Revision history for this message
Vish (vish) wrote :

Ah! I dint realize we could use the 'Other' tab for this. Thanks!
I tried it and noticed what you mention; it does indeed seem confusing.
As you mentioned, testdrive+rsync might be clearer. :-)

Changed in testdrive (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.