- Joined
- Sep 9, 2013
- Messages
- 527 (0.14/day)
| System Name | Can I run it |
|---|---|
| Processor | delidded i9-10900KF @ 5.1Ghz SVID best case scenario +LLC5+Supercool direct die waterblock |
| Motherboard | ASUS Maximus XII Apex 2801 BIOS |
| Cooling | Main = GTS 360 GTX 240, EK PE 360,XSPC EX 360,2x EK-XRES 100 Revo D5 PWM, 12x T30, AC High Flow Next |
| Memory | 2x16GB TridentZ 3600@4600 16-16-16-36@1.61V+EK Monarch, Separate loop with GTS 120&Freezemod DDC |
| Video Card(s) | Gigabyte RTX 3080 Ti Gaming OC @ 0.762V 1785Mhz core 20.8Gbps mem + Barrow full cover waterblock |
| Storage | Transcend PCIE 220S 1TB (main), WD Blue 3D NAND 250GB for OC testing, Seagate Barracuda 4TB |
| Display(s) | Samsung Odyssey OLED G9 49" 5120x1440 240Hz calibrated by X-Rite i1 Display Pro Plus |
| Case | Thermaltake View 71 |
| Audio Device(s) | Q Acoustics M20 HD speakers with Q Acoustics QB12 subwoofer |
| Power Supply | Silverstone ST-1200 PTS 1200W 80+ Platinum |
| Mouse | Logitech G Pro Wireless |
| Keyboard | Logitech G913 (GL Linear) |
| Software | Windows 11 |
This is part 1 of the test. It take 3-4 days just to analyse frametimes in just 4 games.
Some of you guys probably know how to overclock RAM and how to adjust primary timings.
But how about optimizing sub-timings like secondary and tertiary timings for gaming ? Let's find out is it worth it...
Test system
i7-8700K @ 5Ghz core and 4.8Ghz uncore
ASRock Z370 Taichi P4.00 2x8GB
DDR4-3500 16-18-18-36-2T (dual ranks double side Hynix AFR)
EVGA GTX 1080 Ti @ 2126 core / 12474 mem
Corsair HX 750W NZXT H440 White
Custom Water Cooling
Windows 10 64 bit 1607
Nvidia 430.64
Record by ShadowPlay
Wait. WTF at the end of each games ? That is the main topic of today. In-depth frametimes analysis.
I feels that this test is deserve for a ton of effort of frametimes analysis. Most of you guys are probably know what is AVG FPS , 1% Low and 0.1% Low.
The next graph is frametimes graph. It show us about smoothness.
The next one is frametimes by percentile graph. Show about frametimes from average (50th percentile) to the most important 99th (1% Low) and 99.9th percentile (0.1% Low).
Pay attention that from 50-95 I divide each scale to 5 while 95-99.9 each scale is just 1 because that areas are the most important metric for smoothness.
Next is Time spent beyond ...ms , it tell us about how much times that the frame render exceed certain milliseconds.
You guys are probably familiar with those numbers.
50ms mean 20 FPS (1000/20=50)
33.3ms mean 30 FPS (1000/30=33.33)
16.67ms mean 60 FPS (1000/60=16.67)
10ms mean 100 FPS (1000/100=10)
8.33ms mean 120 FPS (1000/120=8.33)
6.94ms mean 144 FPS (1000/144=6.94)
Why is this graph important ? It can tell us about smoothness in another dimension. If you want solid 60 FPS "zero" is the best number that should follow 50ms , 33.33ms and 16.67ms graph.
It mean that no frame take time to render more than 16.67ms.
I really hope you enjoyed my test. Part 2 coming soon
TLDW
Some of you guys probably know how to overclock RAM and how to adjust primary timings.
But how about optimizing sub-timings like secondary and tertiary timings for gaming ? Let's find out is it worth it...
Test system
i7-8700K @ 5Ghz core and 4.8Ghz uncore
ASRock Z370 Taichi P4.00 2x8GB
DDR4-3500 16-18-18-36-2T (dual ranks double side Hynix AFR)
EVGA GTX 1080 Ti @ 2126 core / 12474 mem
Corsair HX 750W NZXT H440 White
Custom Water Cooling
Windows 10 64 bit 1607
Nvidia 430.64
Record by ShadowPlay
Wait. WTF at the end of each games ? That is the main topic of today. In-depth frametimes analysis.
I feels that this test is deserve for a ton of effort of frametimes analysis. Most of you guys are probably know what is AVG FPS , 1% Low and 0.1% Low.
The next graph is frametimes graph. It show us about smoothness.
The next one is frametimes by percentile graph. Show about frametimes from average (50th percentile) to the most important 99th (1% Low) and 99.9th percentile (0.1% Low).
Pay attention that from 50-95 I divide each scale to 5 while 95-99.9 each scale is just 1 because that areas are the most important metric for smoothness.
Next is Time spent beyond ...ms , it tell us about how much times that the frame render exceed certain milliseconds.
You guys are probably familiar with those numbers.
50ms mean 20 FPS (1000/20=50)
33.3ms mean 30 FPS (1000/30=33.33)
16.67ms mean 60 FPS (1000/60=16.67)
10ms mean 100 FPS (1000/100=10)
8.33ms mean 120 FPS (1000/120=8.33)
6.94ms mean 144 FPS (1000/144=6.94)
Why is this graph important ? It can tell us about smoothness in another dimension. If you want solid 60 FPS "zero" is the best number that should follow 50ms , 33.33ms and 16.67ms graph.
It mean that no frame take time to render more than 16.67ms.
I really hope you enjoyed my test. Part 2 coming soon
TLDW
auto sub-timings
optimized sub-timing for Hynix AFR
Comment : results are probably within margin of error. Time spend beyond...ms looks a bit better for optimized sub-timings though.
Comment : still within margin of error. Noticeable less stutter on optimized sub-timings though.
Comment : 3.5% better avg fps and a better looking time spend beyond...ms for optimized sub-timings.
Comment : 4.3% better avg fps plus a bit better on time spend beyond...ms for optimized sub-timings.
Part 2 (SOTTR , CIV 6 , Witcher 3 , TW:WH2 coming soon).
optimized sub-timing for Hynix AFR
Comment : results are probably within margin of error. Time spend beyond...ms looks a bit better for optimized sub-timings though.
Comment : still within margin of error. Noticeable less stutter on optimized sub-timings though.
Comment : 3.5% better avg fps and a better looking time spend beyond...ms for optimized sub-timings.
Comment : 4.3% better avg fps plus a bit better on time spend beyond...ms for optimized sub-timings.
Part 2 (SOTTR , CIV 6 , Witcher 3 , TW:WH2 coming soon).
