On 08/26/2012 04:03 AM, arn...@skeeve.com wrote: > Running > > ./configure && make && make check > > in the gawk master branch takes close to half an hour, maybe more! On > simlar hardware under Linux, it takes less than a minute.
I've found on my hardware that launching a new process in Windows is very slow compared with Linux. With a Fedora 14 host and a Windows 7 VM using VirtualBox, I measured process launch times under 1 ms on Linux, but nearly 100 ms on Windows. Both configure and make rely heavily on launching processes during the build. In my case, it amounted to a 7-10 factor slowdown when building a certain project at work. I had similar problems when trying to launch a Bash prompt under Cygwin, since shell scripts tend to launch a lot of processes as well. I don't believe this problem is caused by Cygwin, at least in my case. I measure the same terrible process launch times using cmd.exe and a batch file, without any Cygwin tools running. You might try benchmarking process launch times on your Windows and Linux setups to see if that might be underlying your problem. I haven't determined whether this is inherently a problem with Windows process launching, or if something I've got installed or mis-configured might be causing the slowdown, so treat this as a hint rather than as publication-quality conclusions to start an OS war on Slashdot :-) Michael Henry -- 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