WTF? Overclocking Reducing FPS???

[Redrooster]

I put the Core Volt to 100%

I set the power limit to 100%

Temp limit to 88c (the most it would let me)

I was able to get a steady +100 MHz to the Core Clock

All's good so far, I started with 89 fps and got it to 94 fps with all the steps to this point.

 

Then I went to start boosting Memory Clock. I bumped it up 30 MHz, and I went to 93.9 fps.

I figured since it's such a small difference, it was within the margin of error.

I then boost the Memory Clock +50 MHz, then I got 89 fps.

I boost the Memory Clock 75 MHz and I was getting 73 fps...

What's going on here???

[SkilledRebuilds]

That can happen. GN and Various YTbers have mentioned this mechanic at play with Memory Overclocking.

 

Its likely having Memory issues behind the scenes, trying to error correct (not artifact) and loses effeciency.

 

It also can depend on the Benchmark run and if it naturally swings a little bit anyway...

Reduce Memory clocks again to where you don't drop off.

[Chris Pratt]

Are you talking about the FCLK? That needs to match the speed of your memory (the actual clocks, not the DDR clocks). In other words, if you have 3600MHz RAM, then the FCLK should be 1800MHz. If you take the FCLK out of step with your RAM speed, then it goes 2:1, which will result in drastically reduced performance.

[LIGISTX]

5 minutes ago, Redrooster said:

I put the Core Volt to 100%

I set the power limit to 100%

Temp limit to 88c (the most it would let me)

I was able to get a steady +100 MHz to the Core Clock

All's good so far, I started with 89 fps and got it to 94 fps with all the steps to this point.

 

Then I went to start boosting Memory Clock. I bumped it up 30 MHz, and I went to 93.9 fps.

I figured since it's such a small difference, it was within the margin of error.

I then boost the Memory Clock +50 MHz, then I got 89 fps.

I boost the Memory Clock 75 MHz and I was getting 73 fps...

What's going on here???

75 MHz in a 2080..? That’s basically a guarantee for a 2080. Most do 400+ no problem.

 

Also though, you likely don’t need to push the voltage. Up the power and temp limits and see what that does. Adding voltage typically has very, very little affect, just makes it run warmer. How are you benchmarking it? What app are you running to give you these FPS numbers?

[LIGISTX]

1 minute ago, Chris Pratt said:

Are you talking about the FCLK? That needs to match the speed of your memory (the actual clocks, not the DDR clocks). In other words, if you have 3600MHz RAM, then the FCLK should be 1800MHz. If you take the FCLK out of step with your RAM speed, then it goes 2:1, which will result in drastically reduced performance.

Based on the fact he is taking about 100% power and temp limit 88c, I assume GPU...

[Chris Pratt]

1 minute ago, LIGISTX said:

75 MHz in a 2080..? That’s basically a guarantee for a 2080. Most do 400+ no problem.

 

Also though, you likely don’t need to push the voltage. Up the power and temp limits and see what that does. Adding voltage typically has very, very little affect, just makes it run warmer. How are you benchmarking it? What app are you running to give you these FPS numbers?

Oh. I went right to CPU. I guess it should be asked: what exactly are you overclocking here?

[Redrooster]

6 minutes ago, SkilledRebuilds said:

That can happen. GN and Various YTbers have mentioned this mechanic at play with Memory Overclocking.

 

Its likely having Memory issues behind the scenes, trying to error correct (not artifact) and loses effeciency.

 

It also can depend on the Benchmark run and if it naturally swings a little bit anyway...

Reduce Memory clocks again to where you don't drop off.

I set the Memory Clock back to default and I got 94.4 fps, and Im using Heaven 4 for the stress and MSI Afterburner for the OC

[Redrooster]

3 minutes ago, Chris Pratt said:

Oh. I went right to CPU. I guess it should be asked: what exactly are you overclocking here?

Oh, I guess I should've clarified (even though this is the Graphics Card section) Im attempting to overclock my 2080 Super

[Redrooster]

7 minutes ago, LIGISTX said:

75 MHz in a 2080..? That’s basically a guarantee for a 2080. Most do 400+ no problem.

 

Also though, you likely don’t need to push the voltage. Up the power and temp limits and see what that does. Adding voltage typically has very, very little affect, just makes it run warmer. How are you benchmarking it? What app are you running to give you these FPS numbers?

Heaven 4.0 for the stress test, and MSI Afterburner

[Chris Pratt]

4 minutes ago, Redrooster said:

Oh, I guess I should've clarified (even though this is the Graphics Card section) Im attempting to overclock my 2080 Super

Yeah, I should have noticed that, but I got here through recent posts, not the graphics card section.

[LIGISTX]

8 minutes ago, Redrooster said:

Heaven 4.0 for the stress test, and MSI Afterburner

Your doing a benchmark run and the average FPS result changed that much?

 

If that is the case. It’s possible your RAM just won’t OC worth anything. Strange, but possible. Drop your voltage back to stock, it’s possible it’s “robbing” the available board power for the GPU core and the RAM isn’t getting enough. 

[Redrooster]

38 minutes ago, LIGISTX said:

Your doing a benchmark run and the average FPS result changed that much?

 

If that is the case. It’s possible your RAM just won’t OC worth anything. Strange, but possible. Drop your voltage back to stock, it’s possible it’s “robbing” the available board power for the GPU core and the RAM isn’t getting enough. 

It worked! for some reason... Okay, so I reset the core volt and mem clock back to the default settings. After that, I tried just boosting the Memory Clock. And yeah, I'm up to +600 boost to the Memory Clock and I've gained a couple fps. Thanks! Also, a funny little aside, I forgot to remove the fps cap that I set on RTSS (170fps, I have a 1440p 165hz display, I don't need 500 fps when I'm playing old games). So the results that I'm getting from Heaven 4.0 are getting bottlenecked by my FPS cap, lmao (there are a few times in the benchmark where it sits at 170 for a few seconds).