Mail Archives: djgpp/1999/06/16/11:50:45
>My notion of slow-down when running on Windows is taken from
configuring
>and building large GNU packages, those where it takes more than 10
minutes
>to run the configure scripts and Make. Overall, on the same machine
which
>is higly optimized for DJGPP programs both in DOS and in Windows, I
>usually get 30%-40% slow-down for the same task when running from
>Windows. That's running only one active DOS box under Windows, and
no
>other Windows programs. For example, what takes 20 minutes from
Windows
>would usually take about 12 minutes from DOS.
>
>I have never been able to figure out just what it is in Windows that
takes
>so many CPU cycles. Interestingly enough, if I do something else
while
>the compilation runs, like read my mail with Emacs, or type some
code
>into the editor, the compilation time is unchanged. So apparently
>multi-tasking other virtual machines is NOT what steals the CPU
cycles.
Well typing into an editor has high delays which will give time back
to windows. The 'dos idle interrupt' is used by keyboard handler
which will give up time while you are typing (remember that the comp
works at 200 or so MILLION cycles and typing requires so little
time). If you ran two builds you would notice a huge slow down.
The intitial slow down is from windows which will still swap and give
time to explorer and the start menu (I think they are seperate
tasks...). So you will always have some delay. Also disk/io is
buffered differntly under windows (VCACHE).
Your build while editing probably took longer but not noticebly as
much.
btw, what is this thread (in the subject) actualy about? testing
compilers or windows?
Tom
+--------------------------------------------------------------------------+
| The coolest site for free home pages, email, chat, e-cards, movie info.. |
| http://www.goplay.com - it's time to Go Play! |
+--------------------------------------------------------------------------+
- Raw text -