When no applications are running, DOSBox still takes quite a lot of CPU usage. Shouldn't DOSBox take almost no CPU usage when there's no applications running? By the way, the Linux DOSEmu takes much less CPU usage because "idle CPU time" is implemented.
idle time is implemented.
the time spend is the time needed to update the screen.
(at least when you are in the prompt.)
Water flows down the stream
How to ask questions the smart way!
wrote:idle time is implemented.
the time spend is the time needed to update the screen.
(at least when you are in the prompt.)
Then why does the CPU usage of DOSBox go up to about 30% constantly? (It should only use less than 10% when it's idle.)
Seems to work fine on my WinXP Home. With an idle DOSBox my total CPU usage hoovers around 5-8% with an occasional spike at 11-13%.
DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32
wrote:Then why does the CPU usage of DOSBox go up to about 30% constantly? (It should only use less than 10% when it's idle.)
😕
What makes you think that it should only take 10% of your CPU time when idle?
It takes between 35% and 40% out of my Duron 700 at the prompt, using core normal with 3000 cycles, and no frameskip.
Almost 100% on a K63-400, using whatever cycles (yes even 1), unless I use frameskip which reduces the processor usage significantly.
Runs 0-3% on Athlon XP1800+
Yes, it’s my fault.
yeah It's always been on my mind to default frameskip to 1.
little games need the full update speed.
Harekiet doesn't agree to that so I've never commited it.
Water flows down the stream
How to ask questions the smart way!
wrote:yeah It's always been on my mind to default frameskip to 1.
little games need the full update speed.Harekiet doesn't agree to that so I've never commited it.
I agree 😁 I feel like 0 is a waste 😀 Always use 1. Doesn't really matter, though, as one just change the conf file 😀
When dosbox uses more than few % of cpu in idle it means that the graphics output is less than optimum. This also means that all this CPU time is lost drawing the screen, instead of emulation. It helps to check all available outputs (for instance, OpenGL will take a lot of CPU time on ATi cards since DOSBox uses a special nVidia extension which is obviously not supported). Or you might have a crappy graphics card (or missing something important, like AGP drivers) 😁. On my laptop for example, surface for some reason performs much better than all other outputs although it's supposed to be slowest.
surface is THE FASTEST. It is that default scaler normal2x that fuckes up everything. Just turn it off and run in fullscreen
