Add job_stats table to db
Bug #838017 reported by
Lars Butler
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenQuake (deprecated) |
Fix Released
|
Medium
|
Lars Butler | ||
Bug Description
Related to: https:/
To capture job stats, we could simply add a 'job_stats' table to uiapi.
For the first iteration, here is what I had in mind for the table structure:
id (pk)
oq_job_id (fk to uiapi.oq_job)
job_start (datetimestamp)
job_finish (datetimestamp)
num_sites (int)
| Changed in openquake: | |
| milestone: | none → 0.4.3 |
| milestone: | 0.4.3 → none |
| milestone: | none → 0.4.3 |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| assignee: | nobody → Lars Butler (lars-butler) |
Revision history for this message
| Lars Butler (lars-butler) wrote | #1 |
| Changed in openquake: | |
| status: | Confirmed → In Progress |
| Changed in openquake: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Lars Butler (lars-butler) wrote | #2 |
| tags: | added: user-feedback |
| Changed in openquake: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Here's what I was thinking about this table... I'd like to hear other opinions.
When a job is launched, the job code can record the number of sites and the job start time.
When a job completes, the finish time can be record by the job supervisor. I think this makes sense, given the following case: if a job fails part way through a calculation, it would still be useful to know how long the job ran before failing.