- Joined
- Jun 20, 2007
- Messages
- 3,942 (0.64/day)
| System Name | Widow |
|---|---|
| Processor | Ryzen 7600x |
| Motherboard | AsRock B650 HDVM.2 |
| Cooling | CPU : Corsair Hydro XC7 }{ GPU: EK FC 1080 via Magicool 360 III PRO > Photon 170 (D5) |
| Memory | 32GB Gskill Flare X5 |
| Video Card(s) | GTX 1080 TI |
| Storage | Samsung 9series NVM 2TB and Rust |
| Display(s) | Predator X34P/Tempest X270OC @ 120hz / LG W3000h |
| Case | Fractal Define S [Antec Skeleton hanging in hall of fame] |
| Audio Device(s) | Asus Xonar Xense with AKG K612 cans on Monacor SA-100 |
| Power Supply | Seasonic X-850 |
| Mouse | Razer Naga 2014 |
| Software | Windows 11 Pro |
| Benchmark Scores | FFXIV ARR Benchmark 12,883 on i7 2600k 15,098 on AM5 7600x |
Not a fan of the flat clocks/disable boost approach - seems it has become a lot of bro science.
I've yet to encounter any noticeable performance loss because the cards were not running flat out all the time. It reeks of that 'parked core' syndrome when people are desperate to improve performance in a piece of software and won't just accept that the software is poorly written, so they start tinkering with things that are not needed and in the end it's all placebo.
I like dynamic live clocks - keeps temperatures down and doesn't waste energy. Meanwhile on any program that requires it, they do use the maximum clocks.
The only time I would support this, is for synthetic testing and you can't have any hiccups as it would affect score. Yet for normal game playing? It's only a problem if it's really a problem - and
you'll know when it is - like a driver bug.
As always with TechPowerUP threads, we need a car analogy :
Synthetic vs real world, is like drag racing at the strip versus drag racing on the street. At the strip every bit of weight counts, every second matters - you're racing for times and slips. On the street, an extra tire in the back, a friend in the passenger seat or an air conditioning unit isn't going to stop you from losing by a fender.
I've yet to encounter any noticeable performance loss because the cards were not running flat out all the time. It reeks of that 'parked core' syndrome when people are desperate to improve performance in a piece of software and won't just accept that the software is poorly written, so they start tinkering with things that are not needed and in the end it's all placebo.
I like dynamic live clocks - keeps temperatures down and doesn't waste energy. Meanwhile on any program that requires it, they do use the maximum clocks.
The only time I would support this, is for synthetic testing and you can't have any hiccups as it would affect score. Yet for normal game playing? It's only a problem if it's really a problem - and
you'll know when it is - like a driver bug.
As always with TechPowerUP threads, we need a car analogy :
Synthetic vs real world, is like drag racing at the strip versus drag racing on the street. At the strip every bit of weight counts, every second matters - you're racing for times and slips. On the street, an extra tire in the back, a friend in the passenger seat or an air conditioning unit isn't going to stop you from losing by a fender.
