So at default speed of 10Gbps, memory clock should be 2500MHz.
![octane render forum octane render forum](https://mir-s3-cdn-cf.behance.net/project_modules/disp/8c3c5921615831.5631ceda37e20.jpg)
Just to make things more confusing GDDR5X should be running in QDR at max performance although it can switch to DDR hence perhaps why it was never called GQDR5.
![octane render forum octane render forum](https://forum.reallusion.com/uploads/images/02c2dd9f-b411-41d1-9005-25ce.png)
Since Nvidia defaults are to have P2 memory clocks 1000MT/s lower than P0 this means AB would not be suitable for overclocking P2. Also note that AFAIK Afterburner does not allow individual clocks for memory P0 and P2 but applies the same offset across both. Will see if OCing the CPU eventually will help there.Ĭlick to expand.4174MHz, is that a typo? Note for memory that I was running close to 11200MT/s in P2. thats more like it! But i still want more, at least the magical 300. then i changed Win Power settings from Balanced to Performance and got the score bumped to 283. Could this have some influence?ĮDIT no2.: OCed the cards bit further - core to 99 and VRAM to 309 - this slightly increased the score to from 257/259 to 261. Seems he is running 3930K at 4,4GHz, while i run my 6850K stock. So i could have just bought 2 1070s to have the same performance and saved lot of money. Am i missing something? Or is there really some Win10 issue?ĮDIT: Someone on Octane Forums is getting 263 score with 2 1070s 1987MHz. Especially OCed, when the Afterburner reports cards running at 2113/4174 MHz. Now i run my CPU and RAM stock so far and did not mess with C-states either, but even then i expected my score to be at least in 140-150 range. Definitely not in line with what Dufus posted, i am getting just 249 score stock clocks / 257 score OCed (+91 core, + 204 VRAM), which makes single card score 120/125. Replied to poster but held up while waiting for admin approval once again.Ĭlick to expand.Well, i finally have my new rig with 2 EVGA 1080s FTWs put together and the scores are bit underwhelming too. It remains to be seen if the effect is because of a bursty nature with the CPU or a problem with the bench. This can be done via BIOS setup and enabling high performance mode in Windows. A similar senario can happen with benches for SSD's where CPU is idle while waiting for data from the disk. The bench does not use the CPU constantly it seems so plenty of opportunities for the CPU to enter those idle states.īy disabling package C-States and core states C3-C7 then the CPU should stop at C1 which just halts the clock while leaving the CPU ready to restart execution when required. There can also be some latency as the CPU core voltage is ramped up by the VRM and can be even more with EIST. Waking the CPU may take some tens of microseconds which in compute time is a lot of cycles. If the CPU enters an idle state C3-C7 then it needs to be woken up again to carry on and do some work.
![octane render forum octane render forum](https://i.imgur.com/4dIjBgw.png)
2 FTWs should get 154 x2, thats 308, almost 5x faster, thats decent, and if it translates into real world performance in my own scenes, i wont regret spending the money and not waiting further on 1080Ti or whatever is coming next.ĮDIT> Wait, 173 now at cca 2200? I read 156 and did not look at the pics properly. Bringing not much additional performance due to bad scaling, not so much. What matters to me are the stable clocks at Octane, and if it can go up to 2200, even if in games cant, thats indeed good news. The other thing, these 2200 clocks, are they only achievable in Octane or can your card actually run 3DMark or some demanding game like Witcher on those clocks without crashing? Cause TBH, i am yet to see any test to show 1080 to be stable at those clocks, then again, all the testing is done on the games or benching apps, which i dont care about. I am curious about further development, would love to get some explanation, whats going on.īTW, i dont get the CPU part, do you think CPU utilization has anything to do with this? I always assumed Octane is strictly GPU bound and CPU matters only in regard to the scene loading process and speed of that, but has zero influence on actual rendering. Still interesting, i thought there is weird scaling is related to CUDA core numbers, now it seems it has to do with clocks as well. That said, i am not holding my breath that eventual official version is going to magically solve any performance discrepancies, if it does not scale well now, color me pessimist but i dont believe it will start to scale well later. The Octanebench is actually not up to date and officially does not even support Pascal cards, it only works cause somebody figured out swapping some files from the actual app, where the cards work, to the benching app could help, and indeed it does.