Actions
Bug #2183
openTime statistics for RCV is incorrectly calculated in local launches
Start date:
01/11/2012
Due date:
% Done:
0%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
During understanding #2178 issue, I noticed that time for RCV (and thus for DSCV) isn't consistent. For instance:
<rcv verifier="blast"> <time name="SMT_SOLVER">3380</time> <time name="ALL">670</time> <time name="PBLAST.OPT">570</time> ... </rcv> <dscv> <status>OK</status> <time name="ALL">670</time> <desc></desc> </dscv>
How can the total execution time for RCV and DSCV can be less then their component execution times?
Also you can observe the problem with time calculation at the page with statistics on reference launches: for cluster launches SMT_SOLVER time isn't calculated at all, while for local launches it doesn't summed to a total time of RCV.
Updated by Alexey Khoroshilov over 11 years ago
We should consider CPU Accounting Controller (https://www.kernel.org/doc/Documentation/cgroups/cpuacct.txt) to solve this issue.
Updated by Evgeny Novikov over 11 years ago
- Assignee set to Vitaly Mordan
The most important issue among other related with time/memory!
Actions