Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: time command with shell builtins
- X-seq: zsh-users 28754
- From: Mikael Magnusson <mikachu@xxxxxxxxx>
- To: dominik.vogt@xxxxxx, Zsh Users <zsh-users@xxxxxxx>
- Subject: Re: time command with shell builtins
- Date: Mon, 23 Jan 2023 19:31:12 +0100
- Archived-at: <https://zsh.org/users/28754>
- In-reply-to: <Y86ZkYooJ9Kf4xCE@localhost>
- List-id: <zsh-users.zsh.org>
- References: <Y86OR0DCpwfSYCXU@localhost> <CAN=4vMqSxEr-K1xg+fGc9kh2qfiZ31fy7hoDBRNHXXF6pH8eEg@mail.gmail.com> <Y86ZkYooJ9Kf4xCE@localhost>
On 1/23/23, Dominik Vogt <dominik.vogt@xxxxxx> wrote:
> On Mon, Jan 23, 2023 at 02:42:05PM +0100, Roman Perepelitsa wrote:
>> On Mon, Jan 23, 2023 at 2:40 PM Dominik Vogt <dominik.vogt@xxxxxx> wrote:
>> >
>> > Is it possible to get timing statistics of shell builtins too?
>> > Timing "echo" isn't very interesting, but timing loop constructs
>> > would be:
>> >
>> > $ time while foo; do bar done
>>
>> This:
>>
>> % time ( while foo; do bar; done )
>
> That wasn't really the question. Of course I can time a loop by
> writing a different command, or by putting it in a pipe or file.
>
> $ time echo foo | true
>
> I just want to get timing statistics of loops either explicitly by
> prepending "time" or implicitly with REPORTTIME.
As Bart already mentioned, the answer to your question is "no", but
you can avoid some downsides of the subshell (eg, if your loop has
side effects that are relevant to the rest of the script etc), by
using SECONDS:
% () { typeset -F4 SECONDS=0; sleep 1; () { typeset -F3 SECONDS=0;
sleep 0.43; echo $SECONDS }; sleep 1; echo $SECONDS }
0.431
2.4329
(the downside here is obviously that it doesn't split out cpu/system
time for you, only elapsed time).
--
Mikael Magnusson
Messages sorted by:
Reverse Date,
Date,
Thread,
Author