http://www.overclock.net/t/1636529/watercool-heatkiller-for-amds-tr4
More on the heatkiller block.
-
-
Talon, Cass-Olé, Trafficante and 2 others like this.
-
Robbo99999 Notebook Prophet
-
Simple math: 500W CPU + 300W graphics card + 40W memory + hard drives + fans and pumps + lighting = 840-900+W.
Now, it depends how heavy you are overclocking, what all has to run off the power supply, where on the efficiency curve the psu considered falls, etc. So, really need more for a good answer to this question. If you aren't going to shoot for a high OC on the graphics card or CPU, then no problem. But there is a lot of little things that can add up.Papusan, Mr. Fox and Trafficante like this. -
I agree with @ajc9988 on this. I would recommend going to at least 1200W and getting one of the EVGA PSUs with the 10 year warranty. PSU is not something to cut corners on or settle for "adequate" IMHO.
I'm barely hitting 500W on my system with 160W on the CPU and about 320W with the GPU. The 7960X is going to pull a lot more than 160W when you start spurring it in the flanks like an angry cowboy.Papusan, Trafficante, Jon Webb and 1 other person like this. -
-
Nice system @Mr. Fox, I saw the video, definitely cool. You're looking good brother. I was going to ask you why you went with a 1000 watt PSU. So even when you run SLI the 1000 will still be adequate. I didn't know the 8700K would pull 160watts. Do you think they'll have a hard time cooling that in the p870?
Spartan@HIDevolution and Mr. Fox like this. -
I was shocked it could pull that many watts, too. But, I am glad it can because that makes it even more awesome. It would suck if it were TDP limited. As far as cooling in the new P870, I have no idea. I hope it works out well, but it remains to be seen at this point.Trafficante, Jon Webb and Papusan like this. -
Johnksss, Trafficante, Papusan and 2 others like this.
-
Johnksss, Trafficante, Papusan and 1 other person like this.
-
That is my Skylake ram timings to beat! Just to give you something to shoot for! I don't know about hitting my latency because of the new mesh, but the rest isn't too far off from yours. -
Oh, if you don't have it:
https://hexus.net/gaming/news/pc/111887-watch-dogs-free-pc-gamers-13th-nov/Mr. Fox likes this. -
Hell, you definitely know your sh*t overclocking PC wise. I think you will do well in hwbot. I may not agree with your philosophy on BGA laptops and etc, but you are always a very nice person willing to learn and help so I am sure you will do fine!!
On that note, I may post some numbers about my new desktop soon.... Not going to be very high clock, but lots of cores
The 7960x can pull a lot of power and accounting for VRM inefficiencies, I would not put the second 1080 TI on there.Last edited: Nov 12, 2017Mr. Fox likes this. -
http://hwbot.org/user/ajc9988/
http://hwbot.org/user/mr._fox/
Still jealous he has worked with more hardware than me and crushes me on everything graphics! CPU and ram, I can hold my own, mostly. But that should give you a better context on us as overclockers. -
Robbo99999 Notebook Prophet
-
Edit: @Mr. Fox - My MaxxMem score from the Skylake build
Last edited: Nov 12, 2017Robbo99999 likes this. -
Robbo99999 Notebook Prophet
ajc9988 likes this. -
Interesting that mr.fox actually took my advice, I'm suprised to say the least.
@ajc9988
How much does RAM frequency impact your threadripper build? -
This can show roughly equivalent performance between the two speeds on AIDA, but performance in other benches is practically identical as well. So it isn't the worry some have made it out to be. As with any system, if you are not willing to optimize for your hardware, you won't get performance like this at all. So you try to get as fast and as tight as possible, but sometimes slow and tight is better than fast and loose, as with so many things in life.Mr. Fox, Papusan, Robbo99999 and 1 other person like this. -
Intel i7-8700K Coffee Lake Memory Benchmark AnalysisSpartan@HIDevolution and ajc9988 like this. -
Also, from testing by PCPer, if mesh is used, it also sees reduced latency with speed to a degree. But... -
I used to get awesome MaxxMem scores with DDR3, but my DDR4-3000 and higher are lower than DDR3-2133 and 2400 scores. Is there something I need to do to MaxxMem to make it work correctly with DDR4? It seems to not read things correctly.
Edit: Another observation... if I look at the leader-board for Corona benchmark, it appears having more memory capacity lowers the benchmark results. Everyone with 16GB, with only a few rare exceptions, has higher Corona benchmark scores than those with 32GB or more. Not sure what to think of that.Last edited: Nov 13, 2017ajc9988 likes this. -
Micro$oft CEO Nadella Mocks iPad Users Telling Them To ‘Get A Real Computer’
"Aaccording to Micro$oft CEO Satya Nadella, the iPad is not a "real computer." What with the thin/flimsy JokeBook's his own company have designed/developed and now throw out everywhere to the masses? Micro$oft Surface Pro series? A real computer? Take a brake. What a Moron. Stop talking BS!! All his company push out nowadays, is pure poison and should be totally avoided. And he can't see it, as it's seemsAnd have he forgot that he's company in fact design their newest OS for tablet/phones now and not for "real" computers?
Last edited: Nov 13, 2017 -
The higher capacity observation might be because, the more the modules, the less you are able to push them to higher frequencies. -
The next part comes in the changes for mesh, cache, etc. For example:
Literally, according to MaxxMem, I'm getting less performance from TR than I got out of my 2740qm CPU! Think about that! In other words, the benchmark needs retired as it no longer accurately reflects performance with the changing tech that has since came out. In fact, half the time it read my Skylake as having 150ns latency, which is ludicrous with these sticks and that CPU. So, you aren't crazy, it doesn't work properly anymore (and I have my doubts on it's usefulness for awhile now).
Now, with all of that out of the way, we can get to some of the things I did. First, I ran it in debug windows mode, and I believe I also had Asus ramdisk hosting all of the smaller benchmarks on a 4GB ram drive. Second, priority set to realtime in windows AND set as high as the program allows (there is a priority setting in the program itself). Third is timings. You are running 16-18-18-38-450 T2 at 3200. In comparison, I was running 4000 CL16 20-20-40-310 T2 for my run. So, almost identical timings (slightly looser by cycle, way tighter in ns), but with 800MHz faster. Literally, we are talking 7.5ns on the cas latency. It is pretty insane compared to 9+ns CL. So we need to work on speeding those up or tightening them down.
So, I found a utility today meant to help calculate ram timings for Ryzen. Not all settings translate, but this tool shouldn't be taken as the be all, end all. Instead, it is to be thought of as a guideline. The main thing is getting boot stable and no errors before you start tightening. Sometimes finding a boot solution is hard. So this does some of the math conversion for you and helps give a starting point.
http://www.overclock.net/t/1640919/ryzen-dram-calculator-overclocking-dram
You use Thaiphoon Burner to get the XMP settings, but go to the bottom to switch to ns. You punch in those to the calc, plus target speed, and it converts it for you. Then, use the safe or fast timings to try to boot without error. From there comes a long process of tightening timings, checking with TM5, etc. You'll also need to have AIDA64 to watch the memory and cache reactions, SuperPi to see reactions to the timings, WPrime also reacts to the changes in timings, and even CB reacts. Now, for some of those, I see more reaction on Ryzen than Intel, but SuperPi, especially 32M, is reactive to memory timings. What you are looking for is overall best performance. Sometimes going too tight, even if it isn't giving errors, can hurt performance (but it will be close to as tight as you can go and not kick errors, so you could actually tighten it all down, then loosen certain ones to see how performance reacts). Remember, some of those timings are not a min or max time, they are windows in which to perform certain operations. Too tight, you end the window too soon and the operation has to start over, thereby sucking performance out from your grasp. Too big of a window and it is still sitting there when the next item arrives, usually kicking out errors, or, if nothing else, robbing cycles.
So, hopefully that helps some (and I'll be here for more assistance if you need it on this).
Edit:Attached Files:
Last edited: Nov 13, 2017 -
-
I have been trying to follow this, with minimal success (thus far): [GUIDE] Skylake Memory Timings on Asus Motherboards ! - HWBOT forumLast edited: Nov 13, 2017TBoneSan, bloodhawk, Rage Set and 1 other person like this. -
http://hwbot.org/submission/3707458_
https://www.3dmark.com/3dm05/5545650 | http://hwbot.org/submission/3707452_
https://www.3dmark.com/3dm06/18005647 | http://hwbot.org/submission/3707455_
https://www.3dmark.com/3dmv/5655486 | http://hwbot.org/submission/3707474_
Last edited: Nov 13, 2017Johnksss, bloodhawk, Rage Set and 1 other person like this. -
Last edited: Nov 13, 2017Robbo99999, ajc9988 and Papusan like this. -
Sure buddy, keep telling yourself that
I know you absolutely hate it when I'm right and won't ever want to admit that u were wrong.
Has anyone here pushed their 8700K to 5.4k ghz yet?
I've seen a couple of people who managed to do so on air, but they were reviewers so I think Intel might have given them silicon lottery ticket. -
So, I ditched the pair of ugly blue 140mm fans that didn't move any air to speak of, replaced them with three better 120mm fans. Moved the 2TB HDD and 2 1TB SSDs to the back of the mobo tray. I ordered four Phanteks Halos RGB frames to go on the front panel side of those three fans and the GPU radiator fan. Those RGB frames will plug directly into the mobo RGB headers and sync with my ASUS Aura mobo lighting control scheme.
Cass-Olé, Keith, Robbo99999 and 3 others like this. -
-
Next, you mentioned using mode 2 for the ram. That's good! On Asus boards, they have two algos: 1) I'm going to rip off your head and **** down your throat, and 2) aggressive, but a normal type of aggressive. If mode 1 doesn't work on an Asus board, always try mode 2.
So, generalized memory timing advice:
1) don't be afraid to leave a larger gap than 2 ticks between the CL and RCDWR and RCDRD timings (RCD). I regularly need 3-4 ticks between the two (CL14 18; CL14 17). In fact, you can go even looser if you need to in finding a boot solution.
2) populate the CWL! - Sometimes, the board will use the old, tighter Cas write latency instead of matching it to the CL! That can prevent it from booting A LOT OF THE TIME. Just populating that with the same CL you are trying can save on many no boot situations.
3) The RP DOES NOT have to match the RCD timings. It can be a couple ticks looser (I usually keep it within 2, like 18 20 when trying timings, but the point is, it doesn't have to be the same).
4) RAS is normally calculated as 2*RCD or tCL + tRCD + tRP (so a range is possible). You can do 2*RCD-1 to 2*RCD+10 or more. So sometimes having that looser can help find a boot solution. Try 2*RCD+(5 to 7). That can sometimes help.
5) Keep the RFC Loose. Loosen it up a lot when starting. Like 600 or more. You will tighten it later in the process.
So, those are the first ones to populate to try to find a boot solution. Start with just the CL, then CL and CWL. Then add in the RCD, then the RP. If that still doesn't work, manually enter the RFC. Finally, add in the RAS. If all of that is still not working, then we move onto the RC, the FAW, and potentially the RRDS and RRDL timings with the FAW.
Quick Note - Setting the tREFI and tREFIx9 - When setting these two timings, it is best to be as loose as possible. But, I found with my Asus board that the tREFI fully maxed on being loose kicked errors (specifically bit flips on the memory). That means, if you are having issues, you may want to take a moderate approach to setting those while looking for a boot. Too tight and you will have issues and lower performance, or errors, but too loose can cause errors also. We will loosen them back up later in the process, so just go with something decently high, but not maxed out.
Here AMD put out a little sheet on the meaning of the timings back when Ryzen came out and people were having issues. It is a quick discussion of what the different timings are and do. https://community.amd.com/community/gaming/blog/2017/05/25/community-update-4-lets-talk-dram
They later tested different ram settings (not all applicable on Intel boards) to give a bit of guidance to people trying to OC their ram. It is similar in some ways to the post above by papusan, where the different speeds and timings were tested. https://community.amd.com/community...emory-oc-showdown-frequency-vs-memory-timings
Basically, AMD was trying to educate its users as to how to OC the ram and what to focus on to get better performance. That is how you create enthusiasts, teach them that it isn't that hard and build their confidence in playing with settings they otherwise never would touch in a million years. I'm not trying to overly sing their praises, as these skills are transferable to a large degree between AMD and Intel, but anything to help get people interested in higher performance is AWESOME!
6) Now the tRC. Here is what AMD had to say about it: "Row cycle time, or the number of clock cycles required for a memory row to complete a full operational cycle. Lower values can notably improve performance, but should not be set lower than tRP+tRAS for stability reasons." Generally, they are right. But I still try to tighten it a lot and sometimes tighten it more than this recommendation but not by much. Overall, try doing tRP+tRAS+(5 to 10) to get it booting. This, just like tRAS, acts as a window. tRAS is "the minimum number of cycles that a row has to be active ... to ensure ... enough time to access the information." So a lot of the general guidance is adding up other settings to figure out the amount of time to allow for certain actions (hence, timings). But, back to the point, the tRC effects performance and you will want to get this one low as well.
7) FAW. AMD says "Four activation window, or the time that must elapse before new memory banks can be activated after four ACTIVATE commands have been issued. Configured to a minumum 4x tRRD_S, but values >8x tRRD_S are often used for stability." Now this can get you some speed, but is often overlooked. Also, as you tighten this timing, you may need to, once errors form, try to tighten the tRRDS. When tightening that timing, you may also want to tighten the tRRDL at the same time (I found with my sticks, keeping tRRDL = tRRDS+3 worked well). This can sometimes allow you to get the tFAW tighter than it otherwise would be.
8) Now that the other timings are tightened, it is time to tighten the RFC and loosen the tREFI and tREFIx9.
After all of that work, you should be ready for a drink and to watch what comes from nice, tight timings. @tgipier - to help with your endeavors as well.Last edited: Nov 13, 2017 -
I'm noticing the L3 on those are slower than TR (by 3.5-4x slower), the L2 similar but slightly faster, but the L1 is double TR. You also have about 33% over my read and just under 20% lower latency on the ram. Not to mention 2 cores and 4 threads on me. But nice!Last edited: Nov 13, 2017 -
As an example of timings that the Utility came up with (remember, just a guide)
-
https://www.ekwb.com/shop/ek-furious-vardar-ff5-120-3000rpm
The Vardar Furious fans are double the CFM of the Arctic F12 fans in the front of the chassis now.Last edited: Nov 13, 2017Papusan, Rage Set, bloodhawk and 1 other person like this. -
-
Last edited: Nov 13, 2017 -
But one thing i seriously love about the Vadar's is that that they are definitely a touch quiter than the Noctua's when running at about 1900rpm. -
I'm thinking of, on two rads, having the Vardars pushing with the iPPC3000 pulling. I think that may increase the air flow the most.bloodhawk likes this. -
-
-
On Linux, look at every product sold to teach kids to code. What OS is used? Think of every mobile device that kids come into contact with and most IoT is on. Literally, the younger generation is going to go open source and there is little that can be done about it! Started with my generation with those just younger than myself and the creation of Ubuntu.
But back on M$. They ****ed up when they tried doing too much international market segmentation, charging S. America and parts of Asia HIGHER prices than even retail in the US. And you wonder why they got pirated! Just so much crap from them!TBoneSan, Papusan, Mr. Fox and 1 other person like this. -
-
Done even get me started on the strategies they implement to maximize profits in Asia and their reasoning behind it, its just plain infuriating. -
Edit: and they claim the price is justified due to piracy! If you want to make it less pirated, try making it a reasonable ****ing price for consumers in that market!bloodhawk likes this. -
Robbo99999 Notebook Prophet
Last edited: Nov 13, 2017 -
http://www.news.com.au/finance/busi...a/news-story/158aa7824a22e1e66611c2afb5e7a61a
XD
Their CEO literally dodged the same question multiple time when asked about it umteen times directly to the face.ajc9988 likes this. -
I bought into the AIO is terribru for a good while until some people started running Noctua NH-D15s versus H115i with the replaced fans on Broadwell-E etc and there was a clear benefit.
But... reviewers don't delid, and 5.4 stock chip on air is about as impossible as ron stoppable taking over kim possible's show
I am punny today.
Sent from my OnePlus 1 using a coconutajc9988 likes this.
*Official* NBR Desktop Overclocker's Lounge [laptop owners welcome, too]
Discussion in 'Desktop Hardware' started by Mr. Fox, Nov 5, 2017.