Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 14 Jun 2004 13:47:37 -0500 From: Brian Ford Reply-To: cygwin@cygwin.com To: fergus@bonhard.uklinux.net cc: cygwin@cygwin.com Subject: Re: FW: wish84 incredibly slow In-Reply-To: <200406130626.i5D6QrgN013801@mailgw01.flightsafety.com> Message-ID: References: <200406130626.i5D6QrgN013801@mailgw01.flightsafety.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes On Sun, 13 Jun 2004, fergus wrote: > >> I have been using Cygwin on a very slow Toshiba. > >> I have tried strace -o wish.log /bin/wish84 > >> but get a file an amazing 7000 lines long. > > > Sort wish.log on the first colum and see what calls > > took the longest. > In all cases the longest calls are those of the style > > [main] wish84 ---- normalize_posix_path: Do you have any network drives in your path? > but on every occasion that I tried this experiment, the longest individual > call, dwarfing all others, is a call towards the end (actually 17th from > last in all the examples of wish.log that I tried) beginning > > [unknown ... > > In one instance this call took more than 100 times longer than the next > longest call, but usually the factor was order 10-30. Could you send me the output of "fgrep unknown wish.log". If the list won't accept it, privately is fine. I don't promise to find anything, but I'm at least mildly interested. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/