Originally Posted by kevindd992002
You better learn to comprehend the word "unless". You are saying the same exact opposite as what GeneO's telling us.
GeneO says that most people frequently enter the idle states which is why C3/C6 will kick in and will affect SSD performance.
You are saying, on the other hand, that most of the time the CPU has "jobs" which makes it always in full load and so the C3/C6 settings don't have an effect.
Please correct me if my understanding of what you're saying is wrong. I'm really having a hard time reading your past-tensed words, sorry
"You system enters these states frequently unless
you are running a constant load like Prime 95 or something, which you rarely do."
In this statement: unless you're running "Prime95 or something" - or anything that use CPU processing power, e.g. loading/playing games, rendering, etc - CPU will idle & then CPU will enter C3/C6 states. In my understanding, the "which you rarely do" referring to "Prime 95 or something".
This is my version:-
"Disabling C3/C6 states can improved SSD performance, so the only way to prevent CPU from entering C3/C6 states when C3/C6 enabled
are by preventing the CPU from idling
. I don't think HDD/SSD benchmark tool put enough load to CPU
. So, run something in the background
& run benchmark, see the result."
By "run something" means run anything that load up CPU, preventing it from going to idling & therefore entering sleep states. At the same time run HDD/SSD benchmark, see if the number improves.
In my opinion, HDD/SSD benchmark software doesn't use a lot of processing power & when this happen some cores if not all will enter sleep states. Because of this you got poor result in benchmark. If you disabled C3/C6 states, you get better benchmark because even though the benchmark software doesn't use a lot of processing power, CPU doesn't enter C3/C6 states but it always ready to work (C1 state at least).
I don't know why C3/C6 states can cause poor SSD performance or to be exact poor benchmark result. I do know there's lag when transitioning from C3/C6 to "working" state (C0) but this is microscopic lag, unnoticeable. However, the lag probably enough to cause the SATA controller to "underperform". This is my understanding though.
Let see real world application. Unlike HDD/SSD benchmark software, real world application usually use CPU processing power. For example, when loading/starting games, it definitely use CPU processing power. CPU "wakes" from sleep states, SATA controller managed to "recover" & SSD performs as it should be. This is why many people claims they didn't noticed any difference in performance whether C3/C6 states disabled or enabled because SSD should perform as it should be. Unlike benchmark software, real world doesn't represent performance with numbers. That's why if you want see some numbers, running something in the background to keep CPU loaded & run benchmark.
Regarding "idle", don't confuse it with C3/C6. C3/C6 are CPU sleep states. CPU will idle either C3/C6 states are enabled or disabled. The only difference between the two is the latter CPU doesn't enter C3/C6 states.
English is my second language. I already tried my best.