Klever

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.