From: Ulf N. <ulf...@cn...> - 2007-08-17 18:37:21
|
Hello! I have found that the make (GNU Make version 3.79.1, have try other version) is very slow in the start of building a source. It can take up to 20 sec to start the buildings! (normally on my computer 8sec, outer in the project have longer start time!) We run all same VMWare image of Windows XP Same code in a Linux enviorement (same GNU make version) start building directly! Have try to localize the time out, and found that must be the start of make itself. (Have made a sh script that print a time stamp and then start the make) ==== #!/bin/sh # Scriptname: run_make echo 'Start Time:"' `date` '"' ; make all $1 ==== In the Makefile (first row) have I add following TIME1 = $(shell echo 'Time1="' `date` '"') The all target call the start target and more like all: start lib ... etc in the start target I have start: @echo "Time == $(TIME1)" ; @echo 'Time2="' `date` '"' ; When i run the run_make script I get following result in MinGW/MSYS === ./run_make Start Time:" Fri Aug 17 14:39:52 WEST 2007 " Time == Time1= Fri Aug 17 14:39:59 WEST 2007 Time2=" Fri Aug 17 14:39:59 WEST 2007 " === In Linux === ./run_make Start Time:" Fri Aug 17 14:41:59 WEST 2007 " Time == Time1= Fri Aug 17 14:41:59 WEST 2007 Time2=" Fri Aug 17 14:41:59 WEST 2007 " === With thes result I think the problem is start of the make itself in MinGW/MSYS. Have some one else found simiar problems? Some tip to solve this (spped up the make) Best regards tew |
From: Keith M. <kei...@us...> - 2007-08-17 19:29:07
|
On Friday 17 August 2007 19:37, Ulf Nyman wrote: > I have found that the make (GNU Make version 3.79.1, have try other > version) is very slow in the start of building a source. Yes. Woe32 *is* slow. Ask Bill to explain why he can't deliver performance which comes even close to that of GNU/Linux. > It can take up to 20 sec to start the buildings! I suspect that it's actually slow file system performance that's the culprit. As a crude benchmark, several months ago I ran a timed sequence of 100 pdfroff cycles, (a shell script running a groff through GhostScript pipeline), to format and emit a 12 page PDF document; IIRC, this took the following times for the 100 cycles: ~1.5 mins, on 650MHz AMD-Duron, with 80GB ATA-66 HD, SUSE-10.0 ~35 mins, on 1.7GHz Pentium-4, with similar HD, MSYS-Win2K ~1 hr, on same Pentium-4 box, but with Cygwin instead of MSYS. > With thes result I think the problem is start of the make itself in > MinGW/MSYS. I think the problem is in the Woe32 file system itself; specifically in the time it takes initially, to read the Makefile, or script. > Have some one else found simiar problems? Yes, but I don't think there's much we can do about it; we just have to live with it. > Some tip to solve this (spped up the make) If you want the speed of GNU/Linux, then use GNU/Linux. If you need to develop for Woe32, then either live with the performance penalty, or do as I do, and use a cross-compiler hosted on GNU/Linux. Regards, Keith. |
From: Daniel C. B. <db...@to...> - 2007-08-17 23:29:34
|
On 8/17/07, Keith Marshall <kei...@us...> wrote: > On Friday 17 August 2007 19:37, Ulf Nyman wrote: > > I have found that the make (GNU Make version 3.79.1, have try other > > version) is very slow in the start of building a source. > > Yes. Woe32 *is* slow. Ask Bill to explain why he can't deliver > performance which comes even close to that of GNU/Linux. If he e-mails you an explanation, can you forward it to us? My main interest here, though, is to find out what Woe32 means. I tried google with define:Woe32 definition Woe32 glossary Woe32 wikipedia Woe32 and also search for ``Woe32'' on wikipedia's website and I found nothing relevant. What does it mean? > > It can take up to 20 sec to start the buildings! > > I suspect that it's actually slow file system performance that's the > culprit. As a crude benchmark, several months ago I ran a timed > sequence of 100 pdfroff cycles, (a shell script running a groff through > GhostScript pipeline), to format and emit a 12 page PDF document; > IIRC, this took the following times for the 100 cycles: > > ~1.5 mins, on 650MHz AMD-Duron, with 80GB ATA-66 HD, SUSE-10.0 > ~35 mins, on 1.7GHz Pentium-4, with similar HD, MSYS-Win2K > ~1 hr, on same Pentium-4 box, but with Cygwin instead of MSYS. Using the GNU emacs and msys, in particular, I also notice a very slow file operation sometimes. For instance, when I open a new file --- e-mails, for example, which I usually write from a webmail and I use firefox to call the GNU emacs --- and I write a paragraph, then I save it (C-x C-s), it sometimes takes various seconds of reading my hard drive until it really saves it. If I then write a new string and save it right afterwards, it saves it very quickly. Also, msys loads, but it takes quite a few seconds sometimes for the shell prompt to appear, and usually my hard drive is being read. Sometimes everything is working very well, and I do a simple ``ls'' and there it goes another few seconds of hard drive screaming; but following the sequence with another ``ls'' is quick. I don't know what it is, but I know it's annoying. |
From: Greg C. <chi...@co...> - 2007-08-18 00:09:50
|
On 2007-08-17 23:29Z, Daniel C. Bastos wrote: > On 8/17/07, Keith Marshall <kei...@us...> wrote: >> On Friday 17 August 2007 19:37, Ulf Nyman wrote: >>> I have found that the make (GNU Make version 3.79.1, have try other >>> version) is very slow in the start of building a source. >> Yes. Woe32 *is* slow. Ask Bill to explain why he can't deliver >> performance which comes even close to that of GNU/Linux. > > If he e-mails you an explanation, can you forward it to us? My main > interest here, though, is to find out what Woe32 means. It means ms windows; ms's founder is unlikely to write to Keith. Some processes that run in the background make it slower than it needs to be. Years ago I measured the effect of killing various unneeded processes, and found that the msw "indexing service" made C++ builds run half as fast as they would without it, on a typical computer in my office. Malware-detection software impairs speed significantly, too. |
From: Hugh M. <das...@gm...> - 2007-08-17 23:55:44
|
Hi Keith, On 18/08/07, Keith Marshall wrote: > On Friday 17 August 2007 19:37, Ulf Nyman wrote: > > I have found that the make (GNU Make version 3.79.1, have try other > > version) is very slow in the start of building a source. > > Yes. Woe32 *is* slow. Naturally, the speed comparison will never be the same as GNU/Linux, since one is native, and one is built on top of the Windows environment. > > It can take up to 20 sec to start the buildings! > > I suspect that it's actually slow file system performance that's the > culprit. I had experienced this problem, and found a simple solution, although, it will not probably help Ulf. The firewall was running anti-spyware scans through each file created or accessed, slowing everything down. Hugh |