View Single Post
Old 10-22-2021, 11:32 AM   #6572
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,027
Karma: 4604637
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by Ser4nb2LUY6e View Post
Would it be possible to add a custom column that records how long the last download/update of a book took?
It's a bit complicated to break out story by story with all the foreground/background processing and caching that goes on.

If counted from the initial start with foreground metadata fetching, the time spent on other downloads' metadata fetch would also be counted. If counted from the start of background processing, metadata cached from FG fetching would discount that time.

And should end time be counted before the output file is written (so it can be included in logpage/titlepage) or after the output file is written? Which can be several to many seconds for large stories.

Existing dateCreated metadata is a datetime set on adapter create in the BG task for plugin.

I think I could add a dateDownloadFinished metadata entry set at the end of download (but before output write) pretty easily. Is there a way for Calibre to look up the output file's modified timestamp? That would give you time after output write.

I'm not really interested in trying to profile anymore accurately than that at a user level.

Quote:
Originally Posted by Ser4nb2LUY6e View Post
Maybe also 3 columns that count successful (there was a change), unsuccessful (no change) and failed (error other than "no change) updates?
I believe the existing 'error' column, with 'Save All Errors' checked, already covers that. Split it out as you like with custom columns.
JimmXinu is offline   Reply With Quote