Copying remaining time estimate is not accurate when doing multiple copies

Bug #902095 reported by Pablo Almeida on 2011-12-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nautilus
Confirmed
Wishlist
nautilus (Ubuntu)
Low
Unassigned

Bug Description

When you copy two files (or two set of files) from or to the same disk separately, so that you have two copying progress bars and estimates and one copying process is dealing with an amount of data larger than the other, nautilus calculates the estimate as if both copying processes were going to be running simultaneously until copying is complete, which is not true. Once the smaller set of files finishes, the larger one will get its full speed back and finish sooner than the first estimate actually predicted.

My suggestion: Nautilus should be aware that the second file copy is slowing the first one down, so it should calculate the first's estimate as something like: <estimate for the smaller set of files copy to finish> + <estimate time to copy the amount of data that will be left when the second process ends at both processes speed combined>.

Although this approach may look too simplistic, I think it's better than the rather pessimistic approach we're using right now.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.2.1-0ubuntu3.2
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Fri Dec 9 07:42:49 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: nautilus
UpgradeStatus: Upgraded to oneiric on 2011-10-27 (42 days ago)

Pablo Almeida (pabloalmeidaff9) wrote :
description: updated
summary: - Copying remaining time estimative is not accurate when doing multiple
+ Copying remaining time estimate is not accurate when doing multiple
copies
description: updated
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Pablo Almeida (pabloalmeidaff9) wrote :

Hello.

I've done that and linked the upstream bug through the "Also affects project..." option. I hope I did it right.

Changed in nautilus:
importance: Unknown → Wishlist
status: Unknown → New
Sebastien Bacher (seb128) wrote :

> I've done that and linked the upstream bug through the "Also affects project..." option. I hope I did it right.

yes that's right, thanks Pablo

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

Other bug subscribers

Remote bug watches

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