So, I went on a "boredom rampage" and I've read an article about a guy overclocking his 865 GPU to 865 MHz and reaching Adreno 660-levels of performance and I decided to give it a try and it was awesome.
Problem is, I'm too much of a thinkerer and I pushed the GPU as much as I could. I ended up on 2000 MHz with "TURBO" voltage profile and it's rock solid even on 2100 MHz with the same profile but KonaBess gives me an error if I try to edit the GPU tables after I booted at 2100 MHz.
I even edited the clock profiles to make it smoother, starting from 305 MHz to 600, 800, 1000, 1200, 1400, 1600, 1800 and 2000 with the right voltages.
Now, the battery and SoC temperatures are the same, the battery drain is basically the same, some other fellow modders with the same device (Mi 10T Pro 5G 8/256 with Pixel Experience Plus ROM) didn't manage to hit the same clocks, crashing even with 1000 or 1200 MHz, with my file from the KonaBess app.
So, have I been extremely lucky with the silicon lottery or it's just an illusion?
Please ask if you need ANY benchmark or proof. I've been monitoring the GPU clock with Franco Kernel Manager Live Monitoring and the clock is solid at 2000 MHz and the 3D performance has at first jumped and then slowly climbed, especially on 3DMark Wild Life Extreme. Wild Life Extreme Stress Test is stable the temperatures are fine.
Do you guys have any questions/suggestions/requests?
Edit: Here are some 3DMark runs, both Wild Life and Wild Life Extreme at stock and 2 GHz. I use Greenify, my storage is 94% full and all my processes in the background take up 4 GB of RAM and I didn't touch the bus for the various steppings for the clocks, so I believe that if heavily tuned, this could make a difference.
Problem is, I'm too much of a thinkerer and I pushed the GPU as much as I could. I ended up on 2000 MHz with "TURBO" voltage profile and it's rock solid even on 2100 MHz with the same profile but KonaBess gives me an error if I try to edit the GPU tables after I booted at 2100 MHz.
I even edited the clock profiles to make it smoother, starting from 305 MHz to 600, 800, 1000, 1200, 1400, 1600, 1800 and 2000 with the right voltages.
Now, the battery and SoC temperatures are the same, the battery drain is basically the same, some other fellow modders with the same device (Mi 10T Pro 5G 8/256 with Pixel Experience Plus ROM) didn't manage to hit the same clocks, crashing even with 1000 or 1200 MHz, with my file from the KonaBess app.
So, have I been extremely lucky with the silicon lottery or it's just an illusion?
Please ask if you need ANY benchmark or proof. I've been monitoring the GPU clock with Franco Kernel Manager Live Monitoring and the clock is solid at 2000 MHz and the 3D performance has at first jumped and then slowly climbed, especially on 3DMark Wild Life Extreme. Wild Life Extreme Stress Test is stable the temperatures are fine.
Do you guys have any questions/suggestions/requests?
Edit: Here are some 3DMark runs, both Wild Life and Wild Life Extreme at stock and 2 GHz. I use Greenify, my storage is 94% full and all my processes in the background take up 4 GB of RAM and I didn't touch the bus for the various steppings for the clocks, so I believe that if heavily tuned, this could make a difference.
Attachments
-
Screenshot_20211121-220201_3DMark (Stock).png371.1 KB · Views: 1,753
-
Screenshot_20211121-220344_3DMark (Stock).png372.5 KB · Views: 1,827
-
Screenshot_20211121-220809_KonaBess (Stock).png88.9 KB · Views: 1,680
-
Screenshot_20211121-220820_KonaBess (Stock).png85.7 KB · Views: 1,586
-
Screenshot_20211121-221852_3DMark (2 GHz).png372.7 KB · Views: 1,407
-
Screenshot_20211121-222044_3DMark (2 GHz).png371.3 KB · Views: 1,375
-
Screenshot_20211121-222129_KonaBess (2 GHz).png93 KB · Views: 1,290
-
Screenshot_20211121-222137_KonaBess (2 GHz).png90 KB · Views: 1,837
Last edited: