In article <[EMAIL PROTECTED]>, Chris Faherty wrote: > On Tuesday 17 February 2004 03:08 am, Aaron Ardiri wrote: > >> i think, the speed issues maybe related to the OS - not to the software >> specifically within cygwin. windows XP chews more resources than linux. :) >> give your windows XP box more ram, and - its faster :) >> >> my laptops use a minimum of 768Mb of ram these days - takes no time to >> compile my prc-tools projects :) and, on a slowish 1.2GHz PIII :) > > It doesn't really seem to be doing much.. it just takes forever to compile. > I still think it is something not implemented efficiently. I was using a > 2.4GHz P4 Windows XP laptop and it was still many times slower than my cheap > Athlon and Linux.. though it was fast enough. > > On my box, I also have a Windows 98SE running inside of win4lin. When I > compile in native Linux it is 19 seconds. Using win98se in win4lin it is 5 > minutes. Hardly any activity noticable during the compile.. the hard disk > blinks maybe once every 5 seconds. It's just painfully slow. > > I think it may have something to do with console programming in win32. I > seem to recall an old console project which gained a considerable speedup by > simply making it window-based. I fear that the win32 console stuff is > performance crippled in some way. >
One thing which can slow down Cygwin enormously on Windows is active virus scanners (the on-line variety, which monitors file opens/close/access). This is a real problem when there is a lot of subshell activation (configure, libtool and friends). Running configure in prc-tools with virus scan active took forever for me. When disabling it it ran like a charm. It is at least one order of magnitude difference in elasped time. Of course, cince Cygwin emulates the POSIX calls it will always be slower than Linux on the same hardware. Just my 5 cents ... Ton van Overbeek -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
