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 07:57:29 -0500 [thread overview]
Message-ID: <CABrM6w=z3-w7U=MCJrHfVnQe9nk0G3c3fCbhKBPb_ye3u_YaGA@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMoYDBiYFdpo9v7OG_03DzjGPDGHww_0_wDsc3cbqwndJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
>
>
> Perhaps you can change your code to spawn fewer zsh processes?
I am doing so. But because zsh is much slower than bash, I will not use zsh
for my scripts at all. Only if it is faster than bash, I may consider using
it. I think this is one aspect that zsh developers may consider to optimize.
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.
I just use shebang to call a specific shell for a whole script.
>
> --
Regards,
Peng
next prev parent reply other threads:[~2019-09-06 12:58 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 [this message]
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='CABrM6w=z3-w7U=MCJrHfVnQe9nk0G3c3fCbhKBPb_ye3u_YaGA@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).