Bugzilla – Bug 258
scan time summary
Last modified: 2009-09-08 09:27:17 UTC
On scanning a directory, provide information on "discovery" metrics. i.e. - display how many songs were discovered and how long it took for the scan. Provide "historical" information on the last n number of scans and how long each one took.
--d_scan, --d_info --d_files should provide more than enough of this when one needs to debug or dig for such info.
I've got something I did for my own use, but it would serve to provide this function. It times each import function and spits out the scan time for each as it finishes as part of d_info. As a further extension, it owuld be possible to store the time for recall to the interface later. The start time is stored as the value of the import hash, so its nearly zero overhead.
Created attachment 87 [details] scantime tracking in log This stores the start time of each import in the import hash, then displays the time to completion in the d_info log as each import ends, and when the overall scan ends.
d_info now includes a summary of total scan time, as well as individual times for each import.
Is this resolved?
its resolved as far as I was going to take it for now. if it needs more work, I would want to have some more detailed feedback of the exact format required.
please re-open if there are any specific UI improvements requested for this summary
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.