From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Sebastian Gniazdowski <psprint@zdharma.org>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Performance tests of quoting and dequoting, printf -v turned out slow
Date: Sat, 10 Mar 2018 15:03:11 +0000 [thread overview]
Message-ID: <20180310150311.GA15390@chaz.gmail.com> (raw)
In-Reply-To: <etPan.5aa3991a.596633ab.159ee@zdharma.org>
2018-03-10 09:36:42 +0100, Sebastian Gniazdowski:
[...]
> I only changed method of time measurement in your snippet, and obtained the slowness:
>
> % typeset -F3 SECONDS=0; INPUT='ice as"program" pick"$ZPFX/bin/prll_(qer|bfr)" src"prll.sh" make"install PREFIX=$ZPFX"'; for ((i = 0; i < 50000; i++)); do printf -v OUTPUT '%q' "$INPUT"; done; echo $SECONDS
> 151.137
[...]
>
> Not sure what using `time' instead of $SECONDS does, but above method is less suspected of any side effects.
[...]
More importantly here, the difference is that you have that code
interpreted by your interactive shell that has read your
~/.zshrc, while the "time" version starts a new non-interactive
shell that doesn't read ~/.zshrc to interpret the code.
There is probably something in your interactive shell
environment that is causing that.
What do you see, if you run:
(set -x; repeat 5 printf -v x x)
What's the output of:
type printf
trap
Do you get the same behaviour if you run that same code after
"zsh -f" (a new interactive shell instance that doesn't read
your ~/.zshrc)?
--
Stephane
next prev parent reply other threads:[~2018-03-10 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 6:22 Sebastian Gniazdowski
2018-03-09 13:23 ` Stephane Chazelas
[not found] ` <etPan.5aa28b1e.77e79f33.159ee@AirmailxGenerated.am>
2018-03-09 13:39 ` Sebastian Gniazdowski
2018-03-09 14:53 ` Stephane Chazelas
2018-03-10 8:36 ` Sebastian Gniazdowski
2018-03-10 15:03 ` Stephane Chazelas [this message]
[not found] ` <etPan.5aa3f656.1efba338.159ee@AirmailxGenerated.am>
2018-03-10 16:53 ` Sebastian Gniazdowski
2018-03-10 15:40 ` Oliver Kiddle
2018-03-11 8:33 ` Bart Schaefer
2018-03-13 11:28 ` Sebastian Gniazdowski
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=20180310150311.GA15390@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=psprint@zdharma.org \
--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).