This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: cygwin too slow

Hi Kevin,
   From what I see in ths system information: this is a MS Win 2000 machine
registered to my company. It has Intel Pentium IV CPU of 2.6 GHz and has
522,228 KB RAM. I'm running so few applications at the moment that there is
close to 300 MB still free Memory left. I'm looking into your other points,
but in the meantime thought just provide this info too.


-----Original Message-----
From: []
Sent: Wednesday, November 12, 2003 5:22 PM
Subject: RE: cygwin too slow

I run Cygwin under Win2K and find it lightening fast most of the time. Maybe
the slowness you're experiencing is not down to cygwin itself, but the
machine generally and Win2K's use of resources specifically. 
General advice for running under Win2K might help here - at least worth a
try first - as would some idea of how other things run on this box. It might
be of some help to know what spec of box you are running Win2K on. Something
like a 350 MHz Duron or Celeron with only 128 Mb memory will be easily
overloaded. A 1 GHz or above Pentium or Athlon with 512 Mb memory should
handle most tasks in its stride. 
I would suggest: 
 * Try and remove as much of the surplus Windoze paraphernalia as you dare:
wallpaper, screen savers, extra fonts - they all use a static amount of
resource and contribute very little other than eye candy (a Windoze
 * Have a look at what services are running on your machine, and stop /
disable things which aren't needed. There's heaps of info out there on the
web as to what each service does. 
 * If you have Micro$oft Office on the machine as well, disable things like
'findfast' and any other indexing service unless you really cannot live
without them. 
 * Try making some use of Win2K's performance monitor, or see what you can
download off the web, to investigate any bottlenecks on the machine.
Remember these too use some resource and will probably worsen the problem. 
 * It would be useful to know what other signs the machine shows. For
example: is there much hard drive activity during the delays ? 
Hope the above is of some use to you, with some more info we might be able
to tackle the problem more specifically.
-----Original Message-----
From: koorapati, koundinya []
Sent: 12 November 2003 11:30
To: Brian Ford
Subject: RE: cygwin too slow

I restricted my path to just /usr/local/bin:/usr/bin:/usr/X11R6/bin , but
still there's been no change in slowness that I see with every command. Here
we are given a customized Windows O.S for the company I work, by Dell
(Windows 2000 Pro). This is really mysterious. In strace I'm not able to see
which system call is eating up so much time as when I start a program say
'ls' with strace, I see nothing and only as ls begins to run after getting
loaded, strace throws it's output. I guess strace is also taking it's own
time to run ?. I'm also not sure what tools on windows could be used for
troubleshooting as this is my first close encounter with MS Windows :)


-----Original Message-----
From: Brian Ford []
Sent: Tuesday, November 11, 2003 10:37 PM
To: koorapati, koundinya
Subject: Re: cygwin too slow

On Tue, 11 Nov 2003, koorapati, koundinya wrote:

> But simple commands like ls take this time
> $ time ls -l
> total 23
> drwxr-xr-x    1 kkoorapa mkgroup-        0 Nov 11 17:50 Mail
> -rw-r--r--    1 kkoorapa mkgroup-       39 Nov 10 17:42 t.c
> -rwxr-xr-x    1 kkoorapa mkgroup-    11224 Nov 10 17:40 t.exe
> -rwxr-xr-x    1 kkoorapa mkgroup-    11224 Nov 10 17:43 tt.exe
> real    0m18.115s
> user    0m0.020s
> sys     0m0.010s
WAG, got any network drives in your path, especially ones that are not
accessable?  Where does strace show a long time between system calls?

And, oh yeah:


Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

Unsubscribe info:
Problem reports:

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]