Overclock.net › Forums › Intel › Intel CPUs › Haswell Overclocking Guide [With Statistics]
New Posts  All Forums:Forum Nav:

Haswell Overclocking Guide [With Statistics] - Page 535

post #5341 of 19564
Quote:
Originally Posted by Shanenanigans View Post

They all talk about affecting the speed of the SSD and there's no mention of C6/C7 anywhere. And there's no mention of the excessive writes to the SSD that you claim by having them (C6/C7) on.

With an SSD, since it's marginally faster than a mechanical drive, and because of the chipset, it doesn't really make a difference. On my Evo, I get 539/415 Seq R/W and 94k/57k Random R/W IOPS with all my C-States on. So performance isn't really affected with ANY C-State on or off.

Well it can effect performance,read through,lol,mentions them many times.So whats effecting thier speeds then?Seeing as your so clever.And how the hell is an SSD,lol,'marginally faster than a mechanical drive'wth.gif
I assumed it was to do with writes to SSD,whatever causes it it can effect performance,dramatically in some instances if you take time to read through.I was giving an opinion,I leave C1E and EIST on,C6 and C7 off.My PC still drops voltage when idle,yeah I could save a bit more power,but I choose not too,I'll save that somewhere else.

And you said you noticed it yourself when I first posted,now your aguing with me that it does'nt exist:rolleyes:This may not effect everyone,however it may effect some.Its not like I plucked this out of thin air niether pretending to be an expert.

I'm sure if anyones interested that is capable of reading,they will see what I have read in those links.
Odysseus
(11 items)
 
  
CPUMotherboardGraphicsRAM
i7 4770K Asrock Z87E-ITX Asus GTX760 Direct CU Mini 8GB Patriot Viper 2133mhz 
Hard DriveHard DriveOptical DriveCooling
Seagate 2TB Corsair Force 3 External Corsair H80 
OSPowerCase
Windows 8 64Bit Silverstone 450W SFX Silverstone SG05 
  hide details  
Reply
Odysseus
(11 items)
 
  
CPUMotherboardGraphicsRAM
i7 4770K Asrock Z87E-ITX Asus GTX760 Direct CU Mini 8GB Patriot Viper 2133mhz 
Hard DriveHard DriveOptical DriveCooling
Seagate 2TB Corsair Force 3 External Corsair H80 
OSPowerCase
Windows 8 64Bit Silverstone 450W SFX Silverstone SG05 
  hide details  
Reply
post #5342 of 19564
I think I must have been one of the "lucky" people to end up with a chip from one of the crummiest batches ever. I haven't been able to push mine past 4.3 (1.3v) stable. I had it running at 4.4 at 1.35 for six hours before my first crash, eventually had to raise it to 1.375 just to get it to pass the eight hour mark before crashing. Decided it wasn't worth the effort to go past 4.3 on such an obviously garbage batch. Wasn't even worth spending the extra on the supposedly "unlocked" multiplier. My VID was 1.072...

Using a Maximus VI Gene too, which just adds to the insult.
Edited by Transylvania - 11/11/13 at 7:11pm
post #5343 of 19564
frown.gif 4.5@1.28 crashed at the third run at the second pass. So basically failed at 6th pass. Hey dark do you think that is stable or not?
Upped voltage to 1.285, really don't want voltage to go this high for 4.5. Running x264 again.

Edit: wow,your chip is really bad, sorry to say...frown.gif I guess next Time CPU will be better?
Will try a 6 hour loop, I can't do night loop tho.
Edited by geogga - 11/11/13 at 7:29pm
post #5344 of 19564
Quote:
Originally Posted by Darkwizzie View Post

My current stance is, you can ditch Prime and go with x264 as your stress test. Temps are not as crazy and the temps you see there is what you get (at most) during normal computer usage. So loop x264 overnight and if you pass, you're stable. Even XTU is not as hot as Prime (IIRC) and XTU is a synthetic. Once you're out of temperature headroom doing x264, THEN your only options are to give up, delid, or get better cooling.

I don't know your cooler.

Interesting.

So far this is P95 small stable:

4 Ghz
1.2 Vcore
65 C to 75 C depending on core

I'm working on:

4.2 Ghz
1.25 Vcore
78 C to 88 C depending on core

I tried lowering cache, but that did nothing. @ 1.225 Vcore, I BSOD'd within 5 minutes. So far 1.25 Vcore has been running for 25 minutes.

Also, temps in BF4 seem to be at least 15 C less. I guess it makes sense to just skip P95 then. I ONLY use that for testing stability. I don't fold. The most intensive things I do would be BF4 or maybe a little Handbrake and that's it.

Also, also, I returned my chip back to Intel to try and get a better one, but ended up w/ the same batch from Costa Rica. It's worth noting they definitely do warranty a processor that's been overclocked. I think they just check it physically for any damages. So w/ that in mind, I guess I don't really need to worry about max temps too much.

Thanks so much for providing so much info and helping me along DW, I really appreciate it.
post #5345 of 19564
Quote:
Originally Posted by Jason7890 View Post

Well it can effect performance,read through,lol,mentions them many times.So whats effecting thier speeds then?Seeing as your so clever.And how the hell is an SSD,lol,'marginally faster than a mechanical drive'wth.gif
I assumed it was to do with writes to SSD,whatever causes it it can effect performance,dramatically in some instances if you take time to read through.I was giving an opinion,I leave C1E and EIST on,C6 and C7 off.My PC still drops voltage when idle,yeah I could save a bit more power,but I choose not too,I'll save that somewhere else.

And you said you noticed it yourself when I first posted,now your aguing with me that it does'nt exist:rolleyes:This may not effect everyone,however it may effect some.Its not like I plucked this out of thin air niether pretending to be an expert.

I'm sure if anyones interested that is capable of reading,they will see what I have read in those links.

The point you made was that C6/C7 enabled causes excessive writes to the SSD. I don't see it mentioned anywhere. If you're capable of reading, you should know that. Also, NONE of those chipsets used were Haswell, where this discussion is happening. Also, the performance was affected only on Sandforce drives, which I presume is because they use compression algorithms, which requires CPU.

Do you have a basis for saying that C6/C7 states cause excessive writes to the SSD? Or are you going to link us to a bunch of SSD optimization guides again where no mention of that is made? And then ask me if I can read?
Quote:
Originally Posted by Transylvania View Post

I think I must have been one of the "lucky" people to end up with a chip from one of the crummiest batches ever. I haven't been able to push mine past 4.3 (1.3v) stable. I had it running at 4.4 at 1.35 for six hours before my first crash, eventually had to raise it to 1.375 just to get it to pass the eight hour mark before crashing. Decided it wasn't worth the effort to go past 4.3 on such an obviously garbage batch. Wasn't even worth spending the extra on the supposedly "unlocked" multiplier. My VID was 1.072...

Using a Maximus VI Gene too, which just adds to the insult.

What batch is yours from? Maybe there's a setting you're missing. You can't just up the vcore and multi for haswell. There's a bunch of stuff to change up in there.

It would be helpful if you added your Input Voltage (VRIN), Ring voltage(vRING), multi, uncore multi, VID ( and resultant vcore using hwmonitor or hwinfo ).

Maybe you should try setting your RAM to 1333/1600 without XMP and see if this still occurs.
Edited by Shanenanigans - 11/11/13 at 7:29pm
post #5346 of 19564
Quote:
Originally Posted by Shanenanigans View Post

The point you made was that C6/C7 enabled causes excessive writes to the SSD. I don't see it mentioned anywhere. If you're capable of reading, you should know that. Also, NONE of those chipsets used were Haswell, where this discussion is happening. Also, the performance was affected only on Sandforce drives, which I presume is because they use compression algorithms, which requires CPU.

Do you have a basis for saying that C6/C7 states cause excessive writes to the SSD? Or are you going to link us to a bunch of SSD optimization guides again where no mention of that is made? And then ask me if I can read?

I think what he was trying to refer to is the "excessive writes" that are usually associated with hibernation and the Smart Response feature....
post #5347 of 19564
Quote:
Originally Posted by blaze2210 View Post

I think what he was trying to refer to is the "excessive writes" that are usually associated with hibernation and the Smart Response feature....

If I'm not mistaken, S4 is the hibernate state, where obviously data would be written to the drive. We're talking about CPU low power states here. And as for Smart Response, I think that's a part of Intel's RST, which requires RAID, and it makes an SSD a cache for a mechanical drive.
post #5348 of 19564
Quote:
Originally Posted by Shanenanigans View Post

If I'm not mistaken, S4 is the hibernate state, where obviously data would be written to the drive. We're talking about CPU low power states here. And as for Smart Response, I think that's a part of Intel's RST, which requires RAID, and it makes an SSD a cache for a mechanical drive.

Apologies, Intel is using too many acronyms for me to keep up with. I meant to refer to Rapid Start - where data is being written onto the SSD often, in order to be able to resume from hibernation and sleep states quicker than usual.
post #5349 of 19564
Quote:
Originally Posted by Shanenanigans View Post

They all talk about affecting the speed of the SSD and there's no mention of C6/C7 anywhere. And there's no mention of the excessive writes to the SSD that you claim by having them (C6/C7) on.

With an SSD, since it's marginally faster than a mechanical drive, and because of the chipset, it doesn't really make a difference. On my Evo, I get 539/415 Seq R/W and 94k/57k Random R/W IOPS with all my C-States on. So performance isn't really affected with ANY C-State on or off.

It used to be the case that C states had that impact, especially with QD1 4K read/writes. Today that's not really the case and people don't need to disable them to speed up their drives.

Lastly and though there's been disagreements on this because SW readings can't be trusted, if you simply use C3 you might as well disable it. Ignoring the fact that SW readings may not be 100% accurate, enabling SVID and using XTU, you can see there is no difference in Watts between C3 enabled and C3 disabled. If you use C6/C7 then there is.
Edited by error-id10t - 11/11/13 at 8:06pm
Just a 'puter
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6700K ASUS Maximus VIII Hero iGPU thanks to Nvidia 970 3.5GB Corsair Vengeance LPX CMK8GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Samsung 950 PRO 512GB Crucial M4 256GB RX360 V3 Koolance CPU-380I 
CoolingCoolingOSMonitor
Koolance RP-452X2 Reservoir Koolance PMP-450 12V Variable Speed Pump Windows 10 Pro x64 benq XL2411Z 
KeyboardPowerCaseMouse
logitech G510 Seasonic X-760 Corsair 800D Mionix Castor 
AudioAudio
Creative Sound Blaster X-Fi Titanium HD DT 990 Premium 250Ohm 
  hide details  
Reply
Just a 'puter
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6700K ASUS Maximus VIII Hero iGPU thanks to Nvidia 970 3.5GB Corsair Vengeance LPX CMK8GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Samsung 950 PRO 512GB Crucial M4 256GB RX360 V3 Koolance CPU-380I 
CoolingCoolingOSMonitor
Koolance RP-452X2 Reservoir Koolance PMP-450 12V Variable Speed Pump Windows 10 Pro x64 benq XL2411Z 
KeyboardPowerCaseMouse
logitech G510 Seasonic X-760 Corsair 800D Mionix Castor 
AudioAudio
Creative Sound Blaster X-Fi Titanium HD DT 990 Premium 250Ohm 
  hide details  
Reply
post #5350 of 19564
Quote:
Originally Posted by error-id10t View Post

It used to be the case that C states had that impact, especially with QD1 4K read/writes. Today that's not really the case and people don't need to disable them to speed up their drives.

Lastly and though there's been disagreements on this because SW readings can't be trusted, if you simply use C3 you might as well disable it. Ignoring the fact that SW readings may not be 100% accurate, enabling SVID and using XTU, you can see there is no difference in Watts between C3 enabled and C3 disabled. If you use C6/C7 then there is.

I believe the discussion was about the sleep (or hibernation) causing excess read/write processes on an SSD, which would cause it to wear out faster - not on the speed, or power usage.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Haswell Overclocking Guide [With Statistics]