Quote:
Originally Posted by JimmXinu
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.
|
I'm using the "Background Metadata" option if that makes a difference. (In my experience, for some reason, the total time for the update I daily run on 50 or so stories is always shorter with "background metadata" instead of metadata in the foreground and then download in the background).
With "Background Metadata", there should be a specific time window start to finish for each story?
Quote:
Originally Posted by JimmXinu
I believe the existing 'error' column, with 'Save All Errors' checked, already covers that. Split it out as you like with custom columns.
|
I already have that column, but I'm not sure how that would give me what I want: three integer columns, one of which (depending on outcome) gets incremented by one every time FFF updates that story?