[SOLVED] Windows 10 slower than Windows 7?

Status
Not open for further replies.
Sep 1, 2019
3
0
20
Having used DOS, Windows since W3.x, 95, ME WNT, W2K, etc..etc and Windows 7 since it's release and making the jump to Windows 10 just over a year ago, I have come to the conclusion that Windows 10 is not as deterministic (not sure if this is the correct word) as Windows 7.
I use Visual Studio and several years ago wrote an app similar to a 'Metronome' which gives a one second 'tick' which worked great in Windows 7. However in Windows 10 it does not give a repeatable tick? It does give the correct number of ticks in a minute (So events are being captured) but stutters and stops for maybe 1-2 seconds then gives 2, 3, 4 ticks to catch up? My CPU runs at 3-4% idle, memory at 30% with little or no network activity. I have used 'Resource Monitor' to check as well with the same result.

My System is:
ASUS X87-Pro
Intel i7 Quad Core 4770K (unclocked)
16GB Corsair Vengeance Memory
1TB Samsung SSD, 800GB Free.
Intel HD Graphics 4600 (not into gaming)

BIOS configured as UEFI boot with virtulisation enabled. Startup is approx 15 seconds and shutdown similar.

I have tried disabling as many apps that I can safely do that run in the background.

My conclusion is that Windows 10 internal scheduling of tasks is not as "sleak" or as good as Windows 7?
Has anyone else got any thoughts on this?
 
Having used DOS, Windows since W3.x, 95, ME WNT, W2K, etc..etc and Windows 7 since it's release and making the jump to Windows 10 just over a year ago, I have come to the conclusion that Windows 10 is not as deterministic (not sure if this is the correct word) as Windows 7.

I'm not sure either. Perhaps it would help to know what exactly it is they are determining.

To answer the question posed in the title: Yes, Windows 10 is slower than Windows 7.
 
I'm not sure either. Perhaps it would help to know what exactly it is they are determining.

To answer the question posed in the title: Yes, Windows 10 is slower than Windows 7.
My point is that the OS has options for real time code. Like a metronome. If you don't tell the OS that your software has to run in real time then the OS has the option to preempt you with other things. That might be virus scanning or windows update checks. Does the OS have more stuff going on? Probably. Does your code take advantage of the tools provided to ensure your run-time requirements? Your answers imply no.
 
  • Like
Reactions: akjones
Are you using the high resolution timer? Have you set the process priority to real time? Those are the things to investigate.
Hi Thanks for the quick response.
I tried the process priority and it certainly improves/cures the problem.
I can invoke a Shell command from within the code to do this as the process priority change is lost when the app restarts.
I never thought about using a Hi res timer within the code as it always worked well when running under W7, I will look and try that as well.
Thanks for your help :)
 
I did find another solution to raise the priority of the app, not ideal that you have to do this but:-

Dim myProcess As System.Diagnostics.Process = System.Diagnostics.Process.GetCurrentProcess()
myProcess.PriorityClass = System.Diagnostics.ProcessPriorityClass.AboveNormal

Windows 7 was never a problem??
 
windows 10 changed few things about its timers (compared to older windows)
https://docs.microsoft.com/en-us/windows/win32/sysinfo/acquiring-high-resolution-time-stamps
here u can see older win used hardware timers

win10 changed it to software timers, (for mobile/tablet and whatever hardware without any form of hardware timers)

https://www.overclockers.at/articles/timerbench-ein-benchmark-fuer-windows-timer
here u can check your timer if windows using software or hardware timer
unknown 10mhz = software timers
 
Status
Not open for further replies.