Feature Request: add duration to tasks (i.e. in tooltip or window)

[gitttt54]

Hi,
I would like to quickly and easily see how long a task took during its last run.
It would be great (and hopefully easy to implement) to display the duration in the tooltip when hovering over "PREV RUN" in the "Tasks" section, where the detailed start time is currently shown.
See the Screenshot with the tooltip, where I mean to add the "duration of the task".

[gitttt54]

Also, how would I change the timeformat to 24hours instead of that AM/PM jibberish?

[arabcoders]

Hello,

Regarding how long a task took to run, unfortunately we dont keep the records in db. it's should be showing the task log i.e [23/04 20:20:19]: NOTICE: SYSTEM: Import process completed in '297.6948's for all users.. There are no plans to convert that to be stored in db at this moment.

Regarding the date format, it is hardcoded for now, but it's easy to allow it to be changed client side so it will be added sometime later this week.

[gitttt54]

Thank you,
the reason, I'd like to see how long a task ran, is because I can't figure out, WHY the import/export tasks running so oddily and not scheduled.
Export runs At 30 minutes past the hour
and
Import runs Every hour

still the backend shows something like:
Last Export 10 hours ago
Last Import 2 hours ago

which makes no sense to me.

The last debug log I exported was 9GB(!) so I can't even start to debug the cause... who can analyse 9GB of data?

[arabcoders]

The debug log is currently very noisy, especially with large media libraries, since we log almost everything. greping last 10-20 lines should give you enough info for how long task was run

Also, the displayed last run time is not the actual previous run time. It is currently derived from the cron schedule calculation, so it can be misleading. The next run time should be accurate, but last is being interpreted as “when the task actually ran”, which it is not.

We should probably remove the last value from that view unless we start tracking real task executions. A better long-term option would be to dispatch task-run events and save them in the events log, so you can see exactly when a task actually started or completed.

If that sounds acceptable, I’ll see what I can do.

Also, if your library is that large, I suggest switching to the dev branch for now. It includes major import-performance improvements, with up to around 3x faster imports in some cases.

[arabcoders]

I forgot that we do log events as task_run.xxx even for non manually queued. i have wired them up to be showing via 1fe7290

it should make it in v1.8.0