On Thu, Jul 01, 2010 at 11:50:01AM -0400, "Marc-Andr? H?bert" wrote: >Hello, > >I installed cygwin a few weeks ago and it has always been very slow. >At first I only needed to perform a few tests (I usually work using a >linux VM) so I didn't look too much into it, but now I might need to >use it more and it is simply not usable. > >About every command I do takes about 15 seconds to execute. The delay >seems to come after the command has executed. So if I do "ls" I see >the contents of the directory almost immediately but then I get a >delay before getting back my prompt. > >I did some reading on the mailing list archive for tips, I have >checked that my path does not contain network drive. > >Here are 2 files. >-cygcheck.out done as instructed on the problems page using "cygcheck >-s -v -r > cygcheck.out" >-strace.ls.txt: This was done using "strace ls -l > strace.ls.txt" > >If you look at the last 2 lines of strace.ls.txt: > 30 120175 [main] ls 5532 __to_clock_t: total 00000000 0000002E >14999334 15119509 [main] ls 5532 pinfo::exit: Calling ExitProcess n >0x0, exitcode 0x0 >You can see that the last item is taking an insane amount of time. I >want to point out that if I do "time ls" several times, it will not >always take 15 seconds to execute but most (didn't do stats, but at >least 1/2 probably 3/4) of the time it will.
This probably doesn't mean what you think it means. A large number there does mean that a previous function (__to_clock_t) too a long time to execute. It means that a long time has elapsed since the last time something was written to strace output. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
