From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-21080-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 20359 invoked by alias); 11 Dec 2015 19:01:29 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 21080
Received: (qmail 9575 invoked from network); 11 Dec 2015 19:01:27 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=to:from:subject:message-id:date:user-agent:mime-version
         :content-type:content-transfer-encoding;
        bh=BUczlHFXHDTxHwHshQ3Zxdp3WS96FwGCrED1zBIV3FQ=;
        b=MIU65CfNgSLVfY+m+7Zi9e7kn9cnQVVcz50LXH0NnEujfqt5BRtDy+ntIbbWz/we6+
         cFyYCU538nkA1LsdqRfBj/QEFMqEEF8Vqtf/NuqP3DkfF+c4EigIHkJ2MZXXHVxWULs/
         UUz7Go7xGPv4nHKyUI9wG62bXUtv9F0OMJZdXd9d4g7a/DB14uYxpysCYMdpXtpylPQg
         whSfswfaS4Tz3eHYRmvdrNE412c21auWKfw1I1mopOp8egqA9QY510CS4wN0MoEU6lFi
         rKyiyUMExH/BnS+O6qpWYxbLfbiGi/daI6iv0T+oKeqwpvXdBUVe5FrtWh8mRIj46ebs
         s/gA==
X-Received: by 10.112.55.38 with SMTP id o6mr7166569lbp.38.1449860483481;
        Fri, 11 Dec 2015 11:01:23 -0800 (PST)
To: zsh-users@zsh.org
From: KARBOWSKI Piotr <piotr.karbowski@gmail.com>
Subject: zsh slow and hogs cpu when using */*/*.ext on large file tree
Message-ID: <566B1D81.2090106@gmail.com>
Date: Fri, 11 Dec 2015 20:01:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

I've come a cross issue with zsh where using the */*/*.ebuild on 
Gentoo's portage tree take about 20 secounds and hogs 100% of single CPU 
core before it builds the list of files to act on.

Something like `grep foo */*/*.ebuild` does not even start the grep for 
20 seconds.

Running `find . -maxdepth 3 -name \*.ebuild` or running `grep foo 
*/*/*.ebuild` under bash does not seems to suffer from the same issue.

The system is rather powerful and the storage is on ssd thus I believe 
the issue is within zsh and not the hardware.

-- Piotr.