On 8/17/07, Keith Marshall <keithmarshall@...> 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
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.