When running a large bag (say, 4.5TB with a few hundred large Quicktime files), the process can be really slow. There's no indication that anything is happening, short of looking at the Task Manager (Windows) to see if there's CPU/Process activity associated with bagger/java.
A progress bar, or even displaying the current operation (hashing a given filename, for instance) in the console area, would be a huge help. Though a progress bar would be best, since it gives you some indication of remaining time.
On a reasonably fast i7 workstation running Windows 7, pulling files off a SAN capable of moving data at well over 1GB/s, it can take over 5 hours to run a bag that will fill an uncompressed LTO7 tape. During that time, we have no idea if anything is actually happening.
Version: Bagger 2.7.7
OS: Windows 7 Ultimate, SP1
Steps to reproduce:
When running a large bag (say, 4.5TB with a few hundred large Quicktime files), the process can be really slow. There's no indication that anything is happening, short of looking at the Task Manager (Windows) to see if there's CPU/Process activity associated with bagger/java.
A progress bar, or even displaying the current operation (hashing a given filename, for instance) in the console area, would be a huge help. Though a progress bar would be best, since it gives you some indication of remaining time.
On a reasonably fast i7 workstation running Windows 7, pulling files off a SAN capable of moving data at well over 1GB/s, it can take over 5 hours to run a bag that will fill an uncompressed LTO7 tape. During that time, we have no idea if anything is actually happening.
Version: Bagger 2.7.7 OS: Windows 7 Ultimate, SP1 Steps to reproduce: