From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7880 invoked by alias); 14 Sep 2009 10:29:26 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Date: Mon, 14 Sep 2009 10:29:00 -0000 Message-ID: <1252924166.7879.ezmlm-warn@cygwin.com> From: cygwin-help@cygwin.com To: listarch-cygwin@sourceware.org Content-type: text/plain; charset=us-ascii Subject: ezmlm warning X-SW-Source: 2009-09/txt/msg00291.txt.bz2 Hi! This is the ezmlm program. I'm managing the cygwin@cygwin.com mailing list. Messages to you from the cygwin mailing list seem to have been bouncing. I've attached a copy of the first bounce message I received. If this message bounces too, I will send you a probe. If the probe bounces, I will remove your address from the cygwin mailing list, without further notice. I've kept a list of which messages from the cygwin mailing list have bounced from your address. Copies of these messages may be in the archive. To retrieve a set of messages 123-145 (a maximum of 100 per request), send an empty message to: To receive a subject and author list for the last 100 or so messages, send an empty message to: Here are the message numbers: 154360 --- Enclosed is a copy of the bounce message I received. Return-Path: Received: (qmail 1925 invoked by uid 22791); 2 Sep 2009 17:41:18 -0000 X-SWARE-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Status: No, hits=-0.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from elasmtp-scoter.atl.sa.earthlink.net (HELO elasmtp-scoter.atl.sa.earthlink.net) (209.86.89.67) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Sep 2009 17:41:08 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=uBkfM3lB5G8gmvhVbulvM4OU8yG2UL7NwLQ7s1iJcEbTAK9sKmcfrrF3DMzAjmfC; h=Received:From:To:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:X-MimeOLE:Message-ID:X-ELNK-Trace:X-Originating-IP; Received: from [69.86.53.234] (helo=minid) by elasmtp-scoter.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1MitpT-0001yz-0v for cygwin-return-154360-listarch-cygwin=sourceware.org@cygwin.com; Wed, 02 Sep 2009 13:41:07 -0400 From: "David Tazartes" To: Subject: Re: Simple bash script is slow to execute - appears to be time spent starting commands like ls Date: Wed, 2 Sep 2009 13:41:02 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Acor9IowhH6bCsUmTZCFGGx93XR1UA== X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18049 Message-ID: X-ELNK-Trace: 5bf265d7c89f1e8e1aa676d7e74259b7b3291a7d08dfec79bef146dc33692d298b908557d1707d2b350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 69.86.53.234 Jeremy Bopp wrote: While I believe the usual forking performance issue is probably the largest factor for your problem, you *are* running an instance of Windows Explorer. It's displaying your desktop which as you indicate above is holding the folder containing your work area. My guess is that you're seeing those usage spikes because of that fact. Try working in a tree which is outside of your desktop, maybe in /tmp, and see if that makes any difference for you. I can't reproduce the slowness you're seeing in general however, even in a directory on the desktop, but then I'm running with XP rather than Vista. ----- I didn't achieve any noticeable speedup, and the echo | cut slowness is still there irrespective of directory (no surprise since it doesn't touch any files except /usr/bin/cut). What do you say we focus on the echo | cut slowness problem, since it eliminates lots of variables and is much easier to test.