Markus Grassl on Sun, 30 Oct 2022 22:24:39 +0100


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: suggestion: timer format 

Thanks for the hint.

I didn't know about %#, but I understand that I have to explicitly call it.
The convenient feature of default(time,1) is that I get the timing information without modifying my code. 


Markus


Am 30/10/2022 um 22:18 schrieb Bill Allombert:

Centrum Informatyczne UG: Ta wiadomość e-mail pochodzi spoza Uczelni Fahrenheita. Zachowaj ostrożność. Nie klikaj linków ani nie otwieraj załączników, chyba że rozpoznajesz nadawcę i wiesz, że zawartość jest bezpieczna.
________________________________
UG IT Center: This email comes from outside the Fahrenheit Universities. Use caution. Do not click links or open attachments unless you recognize the sender and know that the content is safe.

On Fri, Oct 21, 2022 at 04:40:07PM +0200, Markus Grassl wrote:

Dear Ruud,

Thanks for the detailed explanation.

My question was to some extent triggered by laziness.

In my code, I just enable the built-in timing information using

   default(timer,1)

which will reported both the total CPU time and the wall clock (real time)
spent on commands, e.g.,

   cpu time = 73h, 13min, 28,457 ms, real time = 2h, 12,222 ms.

Note that you can use %# to get the timing as a number of milli-second instead.

If we want to allow the display to be changed that, we should probably use
strftime.

Cheers,
Bill.