Closed pkolaczk closed 2 years ago
418.000 17146 171419 0.279 1.179 1.422 1.690 1.959 2.144 2.802 5.194 6.554 419.000 16963 169686 0.181 1.163 1.411 1.692 1.993 2.214 4.178 5.726 13.074 420.000 17032 170217 0.238 1.158 1.410 1.694 1.989 2.206 3.994 5.636 6.849 421.000 17194 171957 0.232 1.169 1.415 1.689 1.965 2.154 2.968 5.136 7.905 422.000 17276 172785 0.236 1.177 1.415 1.683 1.953 2.128 2.560 4.624 6.205 423.008 15905 159015 0.255 1.154 1.405 1.687 1.971 2.179 3.492 5.493 77.136 424.001 16995 169992 0.220 1.171 1.414 1.691 1.982 2.195 3.557 79.364 85.393 631.218 16129 161285 0.163 1.196 1.449 1.734 2.033 2.251 3.549 5.923 675.807 SUMMARY STATS ══════════════════════════════════════════════════════════════════════════════════════════════════════════════ Elapsed time [s] 631.223 CPU time [s] 1204.266 CPU utilisation [%] 95.4
The problem happens only in fixed iteration count mode (-d <number of cycles>). It doesn't happen when the duration of the benchmark is specified by time (-d <number of seconds>s)
-d <number of cycles>
-d <number of seconds>s