zsh-users
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
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, 6 Sep 2019 11:35:08 +0200	[thread overview]
Message-ID: <CAN=4vMoYDBiYFdpo9v7OG_03DzjGPDGHww_0_wDsc3cbqwndJQ@mail.gmail.com> (raw)
In-Reply-To: <CABrM6w=0LBy99ePvChBe22v3XZ=JfY_Tbu0Guf8z6zcyALER3Q@mail.gmail.com>

On Thu, Sep 5, 2019 at 10:45 PM Peng Yu <pengyu.ut@gmail.com> wrote:
> > What are you trying to optimize? If you care about the startup time of
> > your interactive shell, 12 ms vs 6.7 ms doesn't make a difference.
>
> It is not for interactive use of zsh/bash. I am making scripts using
> shells. 12 vs 6.7 ms that is 1x or 50% difference depending on which
> way you consider the ratio, which is a quite significant difference.

Perhaps you can change your code to spawn fewer zsh processes?

What does your code look like? I've seen plenty of code that spends
most of its CPU time on forking but I don't recall seeing anything
that calls `zsh -dfc` or the like in a tight loop.

Roman.

  parent reply	other threads:[~2019-09-06  9:36 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 [this message]
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='CAN=4vMoYDBiYFdpo9v7OG_03DzjGPDGHww_0_wDsc3cbqwndJQ@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --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).