DOS app utilisation question
-
:-D Just a tad. Thank you though Tim. A quick squizz of it seems promising even though it is quite technical. I'll pass it on to him and see how it goes. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Morning all. A friend of mine sent me the following:
I am running a dos program [on Windows]. It takes up 98-99 % of the cpu as a process - at first - which is good because it is an analysis that is running. However - after a period of Windows being idle, this percentage drops to around 0-2% of the cpu useage (ie. system idle process now is "taking 98%" again)... I have tried setting the process as a high priority - no difference. I also have tried to right click (in MyComputer) on the *.exe file to adjust the properties (through "misc") to set the idle sensitivity, however I don't have that option... Do you have any idea how I would keep the program running using all the cpu capability I seemingly have...
He is a botanist so it is impressive he knows so much (but don't go laughing at something he may have said wrong, ok? thanks.) Anyway, does anyone have any tips for him? I'd appreciate it, thanks. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
I would guess that it's doing some "non-CPU" work. Try running PerfMon at the same time, with counters to watch processor activity, memory usage, disk I/O and page file usage. My two guesses would be that it's reading or writing big data files on a slow disk or network, or it's using huge amounts of memory and paging like crazy.
-
Morning all. A friend of mine sent me the following:
I am running a dos program [on Windows]. It takes up 98-99 % of the cpu as a process - at first - which is good because it is an analysis that is running. However - after a period of Windows being idle, this percentage drops to around 0-2% of the cpu useage (ie. system idle process now is "taking 98%" again)... I have tried setting the process as a high priority - no difference. I also have tried to right click (in MyComputer) on the *.exe file to adjust the properties (through "misc") to set the idle sensitivity, however I don't have that option... Do you have any idea how I would keep the program running using all the cpu capability I seemingly have...
He is a botanist so it is impressive he knows so much (but don't go laughing at something he may have said wrong, ok? thanks.) Anyway, does anyone have any tips for him? I'd appreciate it, thanks. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
This might be a silly thing to say, but tell him to click the right mouse button in the dos window, and see if it's CPU time goes up again - the default setup for a dos window seems to be that if you click in the window it goes into some kind of selection mode, so you can copy/paste the text - this has the effect of freezing the app The right mouse button cancels this and lets the app run again -- Help me! I'm turning into a grapefruit! Buzzwords!
-
Morning all. A friend of mine sent me the following:
I am running a dos program [on Windows]. It takes up 98-99 % of the cpu as a process - at first - which is good because it is an analysis that is running. However - after a period of Windows being idle, this percentage drops to around 0-2% of the cpu useage (ie. system idle process now is "taking 98%" again)... I have tried setting the process as a high priority - no difference. I also have tried to right click (in MyComputer) on the *.exe file to adjust the properties (through "misc") to set the idle sensitivity, however I don't have that option... Do you have any idea how I would keep the program running using all the cpu capability I seemingly have...
He is a botanist so it is impressive he knows so much (but don't go laughing at something he may have said wrong, ok? thanks.) Anyway, does anyone have any tips for him? I'd appreciate it, thanks. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
Hey Paul You can ask him to try the following :- 1) Run the DOS app in full screen mode and if that doesn't help improve the speed 2) Use Virtual PC to install a DOS 6.22 machine and run the app on that. Nish
-
I would guess that it's doing some "non-CPU" work. Try running PerfMon at the same time, with counters to watch processor activity, memory usage, disk I/O and page file usage. My two guesses would be that it's reading or writing big data files on a slow disk or network, or it's using huge amounts of memory and paging like crazy.
Good points, Graham. I will mention it to him, thanks. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
Hey Paul You can ask him to try the following :- 1) Run the DOS app in full screen mode and if that doesn't help improve the speed 2) Use Virtual PC to install a DOS 6.22 machine and run the app on that. Nish
#2 is a great idea, I'll see if he has VPC or VMWare. ta. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
This might be a silly thing to say, but tell him to click the right mouse button in the dos window, and see if it's CPU time goes up again - the default setup for a dos window seems to be that if you click in the window it goes into some kind of selection mode, so you can copy/paste the text - this has the effect of freezing the app The right mouse button cancels this and lets the app run again -- Help me! I'm turning into a grapefruit! Buzzwords!
Silly or not I have passed it on, might do the trick thanks. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
He is studying for his PhD in botany. The app analyses genetic diversity through generations. An average analysis takes a week to complete, running through millions of generations, which is why he would appreciate it being able to utilise all available CPU time. He can't just trash it. The app, like many research and university apps, is used by thousands worldwide and is quite powerful. They don't bother with upgrading to Windows as it doesn't benefit them (it doesn't need a nice UI.) regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
He should take care, the processor can be burned at such utilisation, such a long time! Seriously!
-
Morning all. A friend of mine sent me the following:
I am running a dos program [on Windows]. It takes up 98-99 % of the cpu as a process - at first - which is good because it is an analysis that is running. However - after a period of Windows being idle, this percentage drops to around 0-2% of the cpu useage (ie. system idle process now is "taking 98%" again)... I have tried setting the process as a high priority - no difference. I also have tried to right click (in MyComputer) on the *.exe file to adjust the properties (through "misc") to set the idle sensitivity, however I don't have that option... Do you have any idea how I would keep the program running using all the cpu capability I seemingly have...
He is a botanist so it is impressive he knows so much (but don't go laughing at something he may have said wrong, ok? thanks.) Anyway, does anyone have any tips for him? I'd appreciate it, thanks. regards, Paul Watson South Africa Colib and WebTwoZero. K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
What Graham said. Load up Perfmon and check disk, memory, network and processor usage. It is probably doing something non-processor intensive and that needs to be optimized. Faster disks, more memory, better network connection etc.
-
He should take care, the processor can be burned at such utilisation, such a long time! Seriously!
If your processor is adequately cooled there's no risk in running at 100% load, if it's not you're playing with fire and are going to kill it sooner or later by accident. IF you can't afford a better heatsink/fan combo underclock it until it will run safely at full load.