From: Jordan Patterson <jordanp@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: ZSH performance regression in 5.8.1.2-test
Date: Mon, 25 Apr 2022 21:03:48 -0600 [thread overview]
Message-ID: <CAHDOzW7JEjW-nkOHWJAzPkzn1DsEOEhc2Am4C53x9Jki7VNmLg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZfumqPJm3D-Yv7Svb=aOh+SBOeJzgwV+ghWuNDzrpUtQ@mail.gmail.com>
On Mon, Apr 25, 2022 at 7:09 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> I'm curious how large is your interactive startup? I just compared
> 5.8.1.2-test with and without the line-buffering patch running
> zsh -xfic 'autoload compinit; compinit -D' 2>>(wc)
> and in order to get any significant difference I need to have compiled
> with --enable-zsh-debug --enable-zsh-mem-debug.
>
> wc gives 55727 lines / 1858616 characters of xtrace output, which
> ought to be enough for a reasonable comparison?
Running that gives me 56619 lines / 1866092 characters. If I run a
benchmark with your command (without tracing), I do see some slowdown,
but not as dramatic a difference as when loading my normal zshrc with
plugins.
Benchmark 1: prefix/5.8/bin/zsh -fic "autoload compinit; compinit -D"
Time (mean ± σ): 295.4 ms ± 4.2 ms [User: 181.9 ms, System: 114.0 ms]
Range (min … max): 289.0 ms … 299.8 ms 10 runs
Benchmark 2: prefix/5.8.1/bin/zsh -fic "autoload compinit; compinit -D"
Time (mean ± σ): 295.1 ms ± 3.4 ms [User: 183.4 ms, System: 112.1 ms]
Range (min … max): 289.8 ms … 299.5 ms 10 runs
Benchmark 3: prefix/5.8.1.2-test/bin/zsh -fic "autoload compinit; compinit -D"
Time (mean ± σ): 365.3 ms ± 4.2 ms [User: 204.8 ms, System: 160.4 ms]
Range (min … max): 358.7 ms … 373.1 ms 10 runs
Summary
'prefix/5.8.1/bin/zsh -fic "autoload compinit; compinit -D"' ran
1.00 ± 0.02 times faster than 'prefix/5.8/bin/zsh -fic "autoload
compinit; compinit -D"'
1.24 ± 0.02 times faster than 'prefix/5.8.1.2-test/bin/zsh -fic
"autoload compinit; compinit -D"'
prev parent reply other threads:[~2022-04-26 3:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 18:16 Jordan Patterson
2022-04-25 18:56 ` Bart Schaefer
2022-04-25 19:20 ` Stephane Chazelas
2022-04-25 21:27 ` Bart Schaefer
2022-04-26 7:01 ` Bart Schaefer
2022-04-26 8:31 ` Peter Stephenson
2022-04-27 0:33 ` Bart Schaefer
2022-04-27 14:11 ` Stephane Chazelas
2022-04-27 15:02 ` Bart Schaefer
2022-04-27 15:07 ` Peter Stephenson
2022-04-27 15:17 ` Bart Schaefer
2022-04-26 14:31 ` Jun. T
2022-04-26 15:15 ` Peter Stephenson
2022-04-27 0:55 ` Bart Schaefer
2022-04-27 9:16 ` Jun T
2022-04-27 0:38 ` Bart Schaefer
2022-04-27 9:34 ` Peter Stephenson
2022-04-27 10:28 ` Jun T
2022-04-27 12:42 ` Jun T
2022-04-27 13:58 ` Jun T
2022-04-27 15:25 ` Bart Schaefer
2022-04-27 16:18 ` Jun. T
2022-04-27 19:54 ` Jordan Patterson
2022-04-28 9:53 ` Jun T
2022-04-28 14:56 ` Bart Schaefer
2022-04-28 18:51 ` Jun. T
2022-04-29 0:28 ` Bart Schaefer
2022-04-29 2:25 ` Jun. T
2022-04-26 1:08 ` Bart Schaefer
2022-04-26 3:03 ` Jordan Patterson [this message]
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=CAHDOzW7JEjW-nkOHWJAzPkzn1DsEOEhc2Am4C53x9Jki7VNmLg@mail.gmail.com \
--to=jordanp@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-workers@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).