Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 18 May 2024 13:23:03 +0000
Post From: Win 10 performance noticably slower than win 7
| [2019-01-13 07:15:41] |
| PeterSt - Posts: 36 |
|
(near/maxing out at 25% on a single core)
Which is to be read as : the thread of concern (utilizing one core at most) is at 100%. Thus SC, FYI, this is indeed maxing out. W10 can utilize tons of more optimizations than W7, although I can't readily think of what this would be in this instance. The main differences will be in the cooling features of the processor and the task scheduler. The former you can't see really, but the latter possibly can be debugged by means of forcing the system into situations that avoid task switching (read : the tast switching itself can start to cause overhead which is killing). Personally I have never done such a thing for this reason, but what I would do just for observations is telling the BIOS that only one core is in use (can be done through MSConfig as well). It is almost useless to talk about these things because it is (has to be) a matter of interaction between you and the system and what to try next etc. What I would most certainly do is observe the time it takes for things to collapse - this is not necessarily right away. Try to see whether the system handles keep increasing (indicating memory leak, though hard to imagine how this would vary per OS). Also open Resource Monitor and observe the processes in there. Open the SC processes and try to boil down what the heavy consumer is. Etc. I only know of one thing that is a general W10 issue often (sadly varying per Build) and that is Network performance. I have no experience with that in regard of CPU usage but I can expect interrupts to occur way to often, that hogging the processor and which doesn't even always show in CPU usage. In order to test this easily, start copying files just over the LAN and best would be to take a bunch of small files (but make it a 1000 or many more, if possible). Copy to and from the destination elsewhere and measure the time it takes. Always do it twice (or more) and never measure the first time. Take care that the destination has written (flushed) everything before a next attempt. Done ? then the same for the other OS. I think it will be fairly easy to detect a slow down under W10 of a couple of times. Sadly that is about all you are using (more heavily) ... the network ... Whether this (the network) is the bottleneck is still to be determined. But I would definitely want that lag out of the way. If you see network issues, try to change to another SMB protocol (tyical W10 sh*t). Etc. etc. etc. But I hope this gives you some clues. |