As you know, there's a well known Anandtech article on the effects of Load Line Calibration (by Asus and other board makers). Anandtech article on 45nm QX9650
Basically the LLC is there to offset the vDroop that overclockers so despise, because it stands in the way of safe overclocking by requiring more vCore than VID would suggest. After reading that article, I've always had my LLC disabled. Since then, I haven't really been able to hit 3.6Ghz on my Yorkfield Q9450. It would boot to Windows, but it would not stabilize under load, and the vDroop would crash the stability tests until I raise vCore more than I am comfortable with, ie. 1.33v in BIOS vCore.
Today I decided to venture out and see how LLC would help overclocking. Right now I'm typing on this rock stable 3.6Ghz, with only 1.275v BIOS vCore, with LLC enabled and everything else stock. The best thing is that the actual vCore is 1.272v (in CPU-z). Interestingly, vCore idle is 1.264v, a few mV lower than the vCore load. This is best example of LLC in action, compensating for the heavier power draw. In a way, you can say LLC is an auto-cheat implemented by Asus and other board makers to help stabilize CPU when there's significant load, ie. the overclocking stability test when the CPUs hit 100%.
Still, I am not sure if LLC is a cure or a curse for overclockers. This is basically a pencil-mod implemented by the board makers (overwriting the Intel spec). LLC definitely seems to improve overclocking ability, at least by not requiring as much vCore, and it also compensates for power draw. On the other hand, based on Anandtech article, it could also potentially hurt the CPU as your system swings backs and forth from load to idle.
Basically the LLC is there to offset the vDroop that overclockers so despise, because it stands in the way of safe overclocking by requiring more vCore than VID would suggest. After reading that article, I've always had my LLC disabled. Since then, I haven't really been able to hit 3.6Ghz on my Yorkfield Q9450. It would boot to Windows, but it would not stabilize under load, and the vDroop would crash the stability tests until I raise vCore more than I am comfortable with, ie. 1.33v in BIOS vCore.
Today I decided to venture out and see how LLC would help overclocking. Right now I'm typing on this rock stable 3.6Ghz, with only 1.275v BIOS vCore, with LLC enabled and everything else stock. The best thing is that the actual vCore is 1.272v (in CPU-z). Interestingly, vCore idle is 1.264v, a few mV lower than the vCore load. This is best example of LLC in action, compensating for the heavier power draw. In a way, you can say LLC is an auto-cheat implemented by Asus and other board makers to help stabilize CPU when there's significant load, ie. the overclocking stability test when the CPUs hit 100%.
Still, I am not sure if LLC is a cure or a curse for overclockers. This is basically a pencil-mod implemented by the board makers (overwriting the Intel spec). LLC definitely seems to improve overclocking ability, at least by not requiring as much vCore, and it also compensates for power draw. On the other hand, based on Anandtech article, it could also potentially hurt the CPU as your system swings backs and forth from load to idle.