From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Zach Riggle <zachriggle@gmail.com>,
Bart Schaefer <schaefer@brasslantern.com>,
Zsh Users <zsh-users@zsh.org>
Subject: Re: Shell startup, aliases vs. functions vs. autoloadable functions, and zcompile benefits
Date: Tue, 30 Nov 2021 09:29:11 +0100 [thread overview]
Message-ID: <CAN=4vMqTUJNKb6LW3MtpT=isogg84O52PLYtqYddgg4tm3-4Qg@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3TJFRKD3DjmR895BFKrJB649j6W=_u8_9fBY2ptprF2tQ@mail.gmail.com>
On Tue, Nov 30, 2021 at 9:10 AM Mikael Magnusson <mikachu@gmail.com> wrote:
>
> On 11/30/21, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
> > On Tue, Nov 30, 2021 at 3:30 AM Zach Riggle <zachriggle@gmail.com> wrote:
> >>
> >> The benchmark I used
> >>
> >> $ hyperfine 'zsh -i -l "exit 0"'
> >>
> >>
> >> Obviously this is not the BEST benchmark [for checking shell startup
> >> time]
> >
> > Obviously. It's the worst or at least a strong contender for the title.
>
> I think it's fine to do this (assuming he actually meant -i -l -c
> "exit 0" (missing -c in the quoted command)), if you don't do any
> weird stuff in your startup files
Indeed, if all of the following conditions are met, the timing of `zsh
-lic exit` is close to zsh startup time:
- No prompt_subst.
- No precmd hooks.
- No zle hooks.
- No exit hooks.
- No HISTFILE.
- No .zlogout.
- No conditioning on ZSH_EXECUTION_STRING.
I don't know if these things are weird but rc files using at least one
of them are common.
> > Since you care about interactive zsh performance, at least skim
> > through the homepage of zsh-bench. It'll save you time.
>
> % ./zsh-bench
> ==> benchmarking login shell of mikaelh ...
> zsh-bench: cannot find prompt; make sure it contains hostname or the
> last part of the current directory
>
> Sadly no time was saved :(.
That's an unorthodox reading of "skim through the homepage".
Roman.
next prev parent reply other threads:[~2021-11-30 8:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 8:10 Zach Riggle
2021-11-27 8:33 ` Roman Perepelitsa
2021-11-27 20:22 ` Bart Schaefer
2021-11-30 2:30 ` Zach Riggle
2021-11-30 4:11 ` Bart Schaefer
2021-11-30 8:18 ` Zach Riggle
2021-11-30 7:51 ` Roman Perepelitsa
2021-11-30 8:10 ` Mikael Magnusson
2021-11-30 8:27 ` Mikael Magnusson
2021-11-30 8:30 ` Zach Riggle
2021-11-30 9:11 ` Roman Perepelitsa
2021-11-30 11:49 ` Zach Riggle
2021-11-30 12:30 ` Roman Perepelitsa
2021-11-30 15:10 ` Zach Riggle
2021-11-30 16:37 ` Bart Schaefer
2021-11-30 16:41 ` Roman Perepelitsa
2021-11-30 8:29 ` Roman Perepelitsa [this message]
2021-11-30 8:25 ` Zach Riggle
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='CAN=4vMqTUJNKb6LW3MtpT=isogg84O52PLYtqYddgg4tm3-4Qg@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zachriggle@gmail.com \
--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).