From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: zsh-users@zsh.org
Subject: Re: zsh slow and hogs cpu when using */*/*.ext on large file tree
Date: Sat, 12 Dec 2015 17:33:35 +0100 [thread overview]
Message-ID: <CAKc7PVBubv+hUDakCfJoypXDTx=WMA6Qm8qE-nFrSTQKhEzGzg@mail.gmail.com> (raw)
In-Reply-To: <CAKc7PVDKGkNqt=Q=rpLUS76wE8vsZmAWCSyQtvXVnPuFtOe5DA@mail.gmail.com>
PS. I wonder if operating system didn't cache the work that zsh has
done. In other words, in such situation, every following run of */*/*
will be fast. That's why I couldn't test this on my machine (which is
OS X) and I asked you to test.
If you are somehow able to overcome operating system optimizations
(i.e. e.g. every run of */*/* on 5.1.1 is 20 seconds long) then the
values you gave are reliable and usable. Otherwise, bash my benefit
from zsh run.
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2015-12-12 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 19:01 KARBOWSKI Piotr
2015-12-11 21:46 ` Sebastian Gniazdowski
2015-12-12 16:06 ` KARBOWSKI Piotr
2015-12-12 16:24 ` Sebastian Gniazdowski
2015-12-12 16:33 ` Sebastian Gniazdowski [this message]
2015-12-12 16:43 ` Piotr Karbowski
2015-12-12 17:03 ` Sebastian Gniazdowski
2015-12-12 17:18 ` Sebastian Gniazdowski
2015-12-12 17:42 ` Bart Schaefer
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='CAKc7PVBubv+hUDakCfJoypXDTx=WMA6Qm8qE-nFrSTQKhEzGzg@mail.gmail.com' \
--to=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).