Bug #7400
closedKlever takes too much time to upload reports
0%
Description
Klever uploads reports very slowly, and if we consider more optimal strategies of solving verification tasks, then verdicts will be produced even faster than they can be uploaded.
For example, checking only 14 rule specifications with all bug kinds in MAV took almost 28 hours (wall time) for uploading all results, whereas all tasks were prepared and solved for 21 hours:
2016-07-12 15:14:01 (core.py:192) CORE INFO> Get version on the basis of the Git repository
2016-07-12 15:14:01 (core.py:046) CORE INFO> Support jobs of format "1"
...
2016-07-13 11:53:08 (core.py:101) CORE INFO> Terminate report files message queue
2016-07-13 11:53:08 (core.py:104) CORE INFO> Wait for uploading all reports
2016-07-13 19:19:15 (session.py:097) CORE INFO> Finish session
2016-07-13 19:19:15 (core.py:127) CORE INFO> Release working directory
2016-07-13 19:19:15 (core.py:131) CORE INFO> Exit with code "0"
Thus, this issue will not allow to check a lot of "simple" rule specifications fast enough with MAV.
Here are a few suggestions:
1. Add parameters to shrink all logs (related to http://forge.ispras.ru/issues/7253).
2. Do not upload anything for safe verdicts (there were 146697 safes, 341 unsafes and 2858 unknowns in the mentioned experiment).
3. Optimize the process of uploading if needed.
Updated by Vitaly Mordan almost 8 years ago
Update: if we do not upload any report for safe verdicts time of uploading for similar experiments is reduced from ~45 hours to ~38 hours.
But in this case we still need to wait for 4 hours after all tasks were solved.
Note, that the archive with the whole task (141970 Safes, 714 Unsafes, 3316) took only 126Mb.
Although this optimization helps a little, it is clear, that optimizations in Bridge uploading are required.
Updated by Evgeny Novikov almost 8 years ago
I added all the related issues. In particular there are some known problems for both Safe and Unsafe reports.
As a "workaround" I would like to have implemented #7368.
This "global" issue requires careful profiling and understanding after known issues like #7302 and #7350 will be fixed. I am sure that several simple optimizations will help to reduce report uploading time in several times. Altogether this will help to reduce it in one or even several orders.
Updated by Evgeny Novikov almost 8 years ago
- Assignee set to Vladimir Gratinskiy
Updated by Evgeny Novikov almost 8 years ago
- Priority changed from Urgent to High
Experiments after implementation of #7368 showed that reports uploading for lightweight verification results don't take too much time as before. So it can be optimized but not now.
Updated by Evgeny Novikov about 7 years ago
- Status changed from New to Rejected
I consider this issue too broad and almost irrelevant. Soon I will open a couple of related but more concrete issues.