zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.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 09:42:06 -0800	[thread overview]
Message-ID: <151212094206.ZM6592@torch.brasslantern.com> (raw)
In-Reply-To: <566C4EA6.5050704@gmail.com>

On Dec 12,  5:43pm, Piotr Karbowski wrote:
}
} Actually it does not seems that 5.1.1 is much slower than 5.2. My report 
} was wrong as the grep did not showed up for 20s as with first X files it 
} wasn't finding anyting, here I've tested with ls.

To get an accurate reading of the time spent by the shell itself, you
should compare a command that generates the list of files and then
throws it away; e.g.

    time zsh -fc '/bin/true */*/*.ebuild'

There's really no way to get timings of the glob without also adding
the shell startup time, so this may be a little off (hence -f to try
to skip as much startup as possible).

To make the zsh time output look like bash's,

    TIMEFMT=$'real\t%E\nuser\t%U\nsys\t%S'

There are a whole lot of other possible values you can put in TIMEFMT in
zsh to get more details about where it might be taking extra.


      parent reply	other threads:[~2015-12-12 17:41 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
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 [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=151212094206.ZM6592@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).