Message-Id: <200412081416.iB8EGPIu023581@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Chris January" To: Cc: Subject: RE: ls taking too long Date: Wed, 8 Dec 2004 14:15:31 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: X-PopBeforeSMTPSenders: chrisjan AT iomo DOT co DOT uk X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - biro.nothard.net X-AntiAbuse: Original Domain - cygwin.com X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - atomice.net X-Source: X-Source-Args: X-Source-Dir: X-IsSubscribed: yes Note-from-DJ: This may be spam > If a directory contains a large number of files (I have > >40000) where most of them are named such that the first > character is a "1" and you do an "ls x*" where only one of > the files begin with x, the ls takes an inordinate amount of > time, but going to a plain dos window and "dir e*" is really fast. The cmd/dos window's filename filtering is done in the kernel, whereas Cygwin's is done in user mode so every file is processed. Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/