Bug #1553
Updated by Anna Maria Bigatti about 3 years ago
Hi,
I was just timing some computations and noticed that the the time it takes to execute a command with @SystemCommand@ is not accounted for with @CpuTime@.
While the manual more or less says that this is the expected behaviour, this is also quite inconvenient, since it is now not possible to accurately time any computations that involve calls to SystemCommand. :/
Example:
<pre><code>t0:=CpuTime();
SystemCommand("sleep 10");
TimeFrom(t0);
</code></pre>
Yes, I could time these computations using TimeOfDay(), but that only has a precision of seconds and may only bring up problems when timing around midnight...
(Here is also a good spot to mention that I miss the simple but often useful @time@ command that (AFAIR) CoCoA-4 offered ;) )
*2021-03* Added function for computing the total time: *ElapsedTime* see #1553-7 #1553.7
I was just timing some computations and noticed that the the time it takes to execute a command with @SystemCommand@ is not accounted for with @CpuTime@.
While the manual more or less says that this is the expected behaviour, this is also quite inconvenient, since it is now not possible to accurately time any computations that involve calls to SystemCommand. :/
Example:
<pre><code>t0:=CpuTime();
SystemCommand("sleep 10");
TimeFrom(t0);
</code></pre>
Yes, I could time these computations using TimeOfDay(), but that only has a precision of seconds and may only bring up problems when timing around midnight...
(Here is also a good spot to mention that I miss the simple but often useful @time@ command that (AFAIR) CoCoA-4 offered ;) )
*2021-03* Added function for computing the total time: *ElapsedTime* see #1553-7 #1553.7