From: dana <dana@dana.is>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: julien.nicoulaud@gmail.com,
Sebastian Gniazdowski <sgniazdowski@gmail.com>,
zsh-users <zsh-users@zsh.org>
Subject: Re: slow startup of zsh (1x slower than bash)
Date: Fri, 7 Dec 2018 12:06:12 -0600 [thread overview]
Message-ID: <1E9C7E67-0E08-44FD-BC61-5E0137B2A833@dana.is> (raw)
In-Reply-To: <CABrM6wkGd4=ikqoZOreovU95MpPe1fparZ+5qse-8fZ4M=3-OQ@mail.gmail.com>
Some of the people on #zsh have seen different results, but `zsh -f`'s start-up
over-head has always been higher for me on every platform i've tested
(specifically Linux@ARM, Linux@x64, and macOS@x64). It's especially noticeable
on the Mac — but all process over-heads are exaggerated on the Mac, so.
I don't worry about it too much, because you make up for it as soon as you're
able to do something that would have required a fork() in another shell, like
sorting an array or resolving a symlink or matching files by attributes.
I suppose it might be annoying to use it for an httpd or Make shell though
dana
next prev parent reply other threads:[~2018-12-07 18:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 16:27 Peng Yu
2018-12-03 17:37 ` Vadim A. Misbakh-Soloviov
2018-12-07 2:19 ` Sebastian Gniazdowski
2018-12-07 2:57 ` Peng Yu
2018-12-07 16:13 ` Julien Nicoulaud
2018-12-07 16:58 ` Peng Yu
2018-12-07 18:06 ` dana [this message]
2019-09-04 10:13 ` Peng Yu
2019-09-05 19:00 ` Roman Perepelitsa
2019-09-05 20:30 ` Peng Yu
2019-09-05 20:37 ` Roman Perepelitsa
2019-09-05 20:45 ` Peng Yu
2019-09-05 21:19 ` Kaio Augusto
2019-09-06 9:35 ` Roman Perepelitsa
2019-09-06 12:57 ` Peng Yu
2019-09-06 13:11 ` Roman Perepelitsa
2019-09-06 13:19 ` Sebastian Gniazdowski
2019-09-06 13:44 ` Peng Yu
2019-09-06 14:10 ` Roman Perepelitsa
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=1E9C7E67-0E08-44FD-BC61-5E0137B2A833@dana.is \
--to=dana@dana.is \
--cc=julien.nicoulaud@gmail.com \
--cc=pengyu.ut@gmail.com \
--cc=sgniazdowski@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).