zsh-users
 help / color / mirror / code / Atom feed
From: Peng Yu <pengyu.ut@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Sebastian Gniazdowski <sgniazdowski@gmail.com>,
	julien.nicoulaud@gmail.com,  zsh-users <zsh-users@zsh.org>
Subject: Re: slow startup of zsh (1x slower than bash)
Date: Fri, 6 Sep 2019 08:44:32 -0500	[thread overview]
Message-ID: <CABrM6wnQhsy6pt7YixsVJakWky0jQ78Eybtb9gGFh_Puu+SGuA@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMommtG_dPmfhWS4VXY-er9QxL4AKY70o-eR7TGw-ejzkA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

> > But because zsh is much slower than bash...
>
> This isn't a fair summary of your benchmark. It would be more accurate
> to say that zsh on some systems may take up to twice as long as bash
> to execute an empty script.


The slow startup is sufficient to deter me from using it as bash can
satisfy most of my usage. Although zsh has certain features that bash has,
I don’t want to trade-off the 2x startup time difference for those features.

I only care about the Unix variants but not Windows. My test is on Mac via
homebrew installations. I don’t think that there will be too much
difference in Linux. But I don’t have a native Linux machine to test.
Whoever has access to a native Linux machine may post the runtime here for
comparison of different OSes.

> Only if it is faster than bash, I may consider using it.
>
> Could you share some details of your environment in which the overhead
> of 6.7 ms per script is OK but 12 ms is not?
>
> When running a script interactively, this difference shouldn't matter.


I build a library that one causes another. In such cases, the startup time
matters, as most of scripts don’t take a long time to run, I don’t want the
startup eat up too much time. I know I can use ‘source’ circumvent this
problem to a certain extent. But having a shorter startup time is still a
good thing. If bash can do it, I don’t think zsh is absolutely unable to do
it.
-- 
Regards,
Peng

  parent reply	other threads:[~2019-09-06 13:45 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
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 [this message]
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=CABrM6wnQhsy6pt7YixsVJakWky0jQ78Eybtb9gGFh_Puu+SGuA@mail.gmail.com \
    --to=pengyu.ut@gmail.com \
    --cc=julien.nicoulaud@gmail.com \
    --cc=roman.perepelitsa@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).