Feature #8491
closedFeature #8149: Think on proper progress evaluation when several jobs are solved at once or/and much computational resources are available
Feature #8446: Fix and improve progress reporting
Update the progress reporting implementation in Bridge
0%
Description
To restore functionality of progress evaluation I propose to do the following changes in Bridge first:
1) Implement a separate request to Bridge (not as a report) with the following data:
{
"total tasks to be generated": 11111,
"tasks failed": 122,
"tasls solved": 500,
"average wall time to finish": 3766,
"wall time spend on solution": 2300
}
This request Core can do several times during the solution.
If Core has several sub-jobs it will not send any data at all or do it as there is the only sub-job.
2) Bridge should just store and visualize the data as is calculating the percentage as (failed + solved) * 100/total.
3) If Core provided data to Bridge and the job has PROCESSING status Bridge should send received data to scheduler during service/get_jobs_and_tasks request adding the following section:
{
....
"jobs progress": {
"job_id": {data as is sent by Core}
}
}
Addiction of the section can be done only on update the data to economy traffic.