zsh-users
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: dominik.vogt@gmx.de, Zsh Users <zsh-users@zsh.org>
Subject: Re: time command with shell builtins
Date: Mon, 23 Jan 2023 19:31:12 +0100	[thread overview]
Message-ID: <CAHYJk3QD8NbCqt0LdXshiVf6W3GQLnDzo6-1mj0qCJOTkHFGRA@mail.gmail.com> (raw)
In-Reply-To: <Y86ZkYooJ9Kf4xCE@localhost>

On 1/23/23, Dominik Vogt <dominik.vogt@gmx.de> 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@gmx.de> 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


  parent reply	other threads:[~2023-01-23 18:32 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 13:40 Dominik Vogt
2023-01-23 13:42 ` Roman Perepelitsa
2023-01-23 14:17   ` zeurkous
2023-01-23 14:23     ` Roman Perepelitsa
2023-01-23 14:40       ` zeurkous
2023-01-23 14:28   ` Dominik Vogt
2023-01-23 14:46     ` zeurkous
2023-01-23 16:31     ` Bart Schaefer
2023-01-23 18:31     ` Mikael Magnusson [this message]
2023-01-23 18:49       ` Dominik Vogt
2023-01-24  9:32         ` Mikael Magnusson
2023-01-24 10:48           ` Dominik Vogt
2023-01-24 23:12             ` Dominik Vogt
2023-01-24 23:36               ` Bart Schaefer
     [not found]                 ` <Y9B7A8dWLiZNXKfW@localhost>
2023-01-26 16:23                   ` Dominik Vogt
2023-01-26 16:56                     ` Bart Schaefer
2023-01-26 17:26                       ` Dominik Vogt
2023-01-26 17:40                         ` Bart Schaefer
2023-02-02 18:10                     ` Dominik Vogt
2023-02-02 18:28                       ` Bart Schaefer
2023-02-02 19:15                         ` Dominik Vogt
2023-02-02 19:15                           ` Dominik Vogt
2023-02-02 19:31                           ` Bart Schaefer
2023-01-24 23:32             ` Bart Schaefer
2023-01-25  7:43               ` Mikael Magnusson
2023-01-25 12:58                 ` Dominik Vogt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAHYJk3QD8NbCqt0LdXshiVf6W3GQLnDzo6-1mj0qCJOTkHFGRA@mail.gmail.com \
    --to=mikachu@gmail.com \
    --cc=dominik.vogt@gmx.de \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).