Differences

This shows you the differences between two versions of the page.

--- start:overclockgwe [2022/05/03 20:54] – peter
+++ start:overclockgwe [2023/09/14 20:19] (current) – peter
@@ Line 1: / Line 1: @@
+__**//This page is out of date - need to find a workable solution for wayland and update it - Pete @ 14/09/2023//**__
 I only have Nvidia cards so cant show how team red users do it :( sorry I dont really play games that much.
 Maybe someone else can create a section for team red :)
@@ Line 23: / Line 25: @@
 With this in mind you can follow along if you make the edits for method 1 above (to revert remove the needs_root_rights line and change allowed_users to 'console').
-Yes if you no longer need the overclocking capabilities you should revert back to the more secure option. I dont really game so while I did leave the setup in this way during the test I did revert once done. However xorg did used to run under root a while ago and some display managers still do (eg: lightdm) so its not such a major security risk that you will immediately die or anything, Im just saying an improvement was introduced a few years ago where gdm changed to rootless and its been like that ever since and other display managers will eventually also run rootless, so yeah, it was fine for years under the old way, and might be fine still but every time you chink away at the armor of your system it becomes just a little bit less secure so...
+Yes if you no longer need the overclocking capabilities you should revert back to the more secure option. I dont really game so while I did leave the setup in this way during the test I did revert once done. However xorg did used to run under root a while ago and some display managers still do (eg: lightdm and probably some others I never use) so its not such a major security risk that you will immediately die or anything, Im just saying an improvement was introduced a few years ago where gdm changed to rootless and its been like that ever since and other display managers will eventually also run rootless, so yeah, it was fine for years under the old way, and might be fine still but every time you chink away at the armor of your system it becomes just a little bit less secure so...
 Once that file is edited you will need to also need to create a file and add some info to it:
@@ Line 40: / Line 42: @@
 EndSection
 </code>
+You will need to reboot for coolbits to take effect at this point. A value of 12 is fairly safe but there are other values you can specify that might be unsafe (eg: overvoltage etc). 12 simply allows changing of fans speed and overclocking the cpu cores which if set too high simply crash the system and you have to reboot.
+Next we install green with envy. This uses flatpak so we type:
+<code>
+sudo apt-get install flatpak
+flatpak --user remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
+flatpak --user install flathub com.leinardi.gwe
+flatpak update
+flatpak run com.leinardi.gwe
+</code>
+You can also run gwe from the apps menu in gnome rather than the cli.
+The app itself if pretty simple, you make an overclock profile and apply it. I didnt bother changing the fan settings but you can if you want to.
+In my test I overclocked the GPU by a value of 272 or increased it from 1911 to 2176 which is about a 13.8% improvement. For memory I used 1000 and it increased the memory clock from 3504 to 4504. It seems like you can just max that out and nothing bad happens.
+When choosing values you should find a value where the system crashes then reduce it by like 20 or more. I found It crashed at like 295 so reduced it down to 272. The memory it seemed you can just set it really high at least for me (to the max).
+If games are unstable at that value keep reducing it by like 10 until games n longer crash while playing. If you temper your expectations to be around 10% then you will be fine.
+{{:images:gwe.png?400|}}
+I do imagine an improvement of around 10% is or can be expected on average but could be card dependent. I dont really game as I mentioned so this is just what I found.
+I have an old card so not really much I can do but here is the before and after in Apex legends where I found an area that was taxing on the card with lots on screen:
+No increase:
+(frames 42)
+{{:images:apex0.jpeg?400|}}
+Overclocked:
+(frames 49, or around 15% increase)
+{{:images:apex1.jpeg?400|}}
+Dont forget you can pass cool options to steam so if you install the gamemoderun package and wanted to limit the game to 60fps so you dont need to use gsync you could add this to the steam options:
+DXVK_FRAME_RATE=60 gamemoderun %command%
+eg:
+{{:images:apexoptions.png?400|}}
+Other options you can try are "-novid" and "DXVK_ASYNC=1". Novid apparently skips the into and if you use proton ge apparently the DXVK setting improves stutter. My personaly feeling is too many options could cause more harm than good so I didn't bother. To add them you would do something like:
+DXVK_FRAME_RATE=60 DXVK_ASYNC=1 gamemoderun %command% -novid
+But you can google around and try some other options if you really want to.

Make Debian Fun Again And Learn How To Do Other Cool Stuff Too

User Tools

Site Tools

Differences

Page Tools