RTX 2060 consumes 115 watts and struggles with high frame rates in CS:GO.
RTX 2060 consumes 115 watts and struggles with high frame rates in CS:GO.
I own a ROG Strix Scar 15 from 2020 featuring a 240Hz display, 3ms refresh rate, an 8-core Intel i7-10875H processor with RTX 2060 graphics, 115W power consumption, and 16GB of RAM. My Windows configuration is already fine-tuned, and I’ve enabled Game Mode. All graphics drivers are up to date, and my power/battery settings are optimized for maximum performance. The NVIDIA control panel is set to high performance mode, with ultra low latency enabled.
In benchmark tests using Ulletical with all settings maximized, I achieved an average frame rate of around 159 FPS overall. During Deathmatch in Dust II, the average dropped to 120-150 FPS, sometimes higher in tunnels. These numbers are quite surprising given my RTX 2060 and the specs.
Comparing to other titles, Apex Legends averaged 100-120 FPS, COD Warzone 80-100 FPS, and PUBG 90-120 FPS under similar conditions. My results seem unusually low for such hardware. I suspect the impact of my CSGO performance is significant, possibly due to its demanding rendering workloads. Even with dual-channel RAM, the difference is noticeable.
I disabled fullscreen optimizations across all games and turned off high DPI scaling in applications. These adjustments should help stabilize performance. The low FPS in CSGO might be related to its complex shaders and multithreaded processing, which can strain even a strong GPU.
Please let me know what you think about these observations—I’d appreciate your insights!
Bandwidth really impacts performance, which explains why many recommend using dual channels along with lower MSAA settings.
i watched a comparison on youtube about single vs dual channel ram, and the gap was about 20 fps. The videos i shared also use 8x msaa, so i expect better performance even then.
just checking how everything works, I also tried it with 4x 2x and it's still running at about 130-150 fps in Deathmatch Dust II. The 8x MSAA isn't causing the issue.
It might be constrained by the CPU, maybe. Also, dual-channel RAM would be really helpful.