Overclocking a Pi 4, yes I checked the stickies and the docs.

[Great_Snake]

@quicksilver The recommended for Retropi, I believe it is called Redream.

[quicksilver]

@Great_Snake did you lower the window resolution to 640x480 in the redream menu?

[Great_Snake]

@DTEAM I notice in your picture quote deal thing you don't have a GPU or a CPU overclock listed, is there a reason for that?

[DTEAM]

@Great_Snake If you talk about gpu_freq, with the Pi4 you don't play with that

From: https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md

*he core_freq of the Raspberry Pi 4 can change from the default if either hdmi_enable_4kp60 or enable_tvout are used, due to relationship between internal clocks and the particular requirements of the requested display modes.

Display option Frequency
Default : 500
enable_tvout : 360
hdmi_enable_4kp60 : 550

Changing core_freq in config.txt is not supported on the Pi 4, any change from the default will almost certainly cause a failure to boot.

It is recommended when overclocking to use the individual frequency settings (isp_freq, v3d_freq etc) rather than gpu_freq, as since it attempts to set core_freq (which cannot be changed on the Pi 4), it is not likely to have the desired effect.*

[IceChes1]

Sonic Adventure lag badly even with an overclock on a Pi 4. Are you guys getting it to run smoothly?

[Great_Snake]

@quicksilver said in Overclocking a Pi 4, yes I checked the stickies and the docs.:

@Great_Snake did you lower the window resolution to 640x480 in the redream menu?

When I do that, it becomes a blurry mess.

[quicksilver]

@Great_Snake said in Overclocking a Pi 4, yes I checked the stickies and the docs.:

@quicksilver said in Overclocking a Pi 4, yes I checked the stickies and the docs.:

@Great_Snake did you lower the window resolution to 640x480 in the redream menu?

When I do that, it becomes a blurry mess.

The redream menu might get a little fuzzier but the actual gameplay shouldnt change that much since it's rendering at 640x480.

[quicksilver]

@IceChes1 sonic adventure 1 or 2? Last I played SA1 it seemed fine to me unless there has been a performance regression in the last couple months.

[Riverstorm]

@Clyde said in Overclocking a Pi 4, yes I checked the stickies and the docs.:

I wouldn't recommend to overclock just "because you can".

I think "because you can" is a good enough. For overclock hobbyists or enthusiasts that reason alone is good enough. There are entire communities dedicated to it. I wouldn't discourage people from exploring this "corner" of Pi hardware while doing a bit of gaming. If they have an interest at all in overclocking I would encourage doing some research first. Some good might come of it and if not it's easy to undo. As long as you understand the pros and cons you should be fine. I did it and I learned a few things through the process so it's a win-win!

The Pi foundation has pages dedicated to overclocking, parameters, arguments, ranges, etc. If they didn't want you to overclock they would probably just bin the chips and remove all the boot commands that facilitate such functionality.

From raspberrypi.org:

We’ve been doing a lot of work to understand the impact of voltage and temperature on lifetime, and are now able to offer a “turbo mode”, which dynamically enables overclock and overvolt under the control of a cpufreq driver, without affecting your warranty.

They have you covered if you want to give it a go!

@quicksilver also from raspberrypi.org

The level of stable overclock you can achieve will depend on your specific Pi and on the quality of your power supply; we suggest that Quake 3 is a good stress test for checking if a particular level is completely stable.

Most components are designed with a tolerance range or safety margin for parameters out of your control like ambient temps, voltage fluctuations, etc. which may work in your favor if your Pi is on top of the manufacturing bell curve.

There is a finite limit to how far you can go with it. Keeping the heat away from the SoC (don't melt the silicon ;) is probably the number one thing you can do to maintain a successful overclock well beyond the usefulness of the Pi and before you're on to the next generation.

Heat really is the killer here if you think about it. Cooling is key until you hit the device's max voltage tolerance and eventual destructive failure but you have to set the turbo bit before going past 1.3125V. Behind cooling always test, test and test your overclock settings for stability on every Pi purchased. They may vary wildly.

As for power it should be pretty minimal. 3A x 5v = 15w. So if I use my Pi 24 hours a day and with the cost of electricity here it would be a little under $10 a year if I am doing the calculations correctly.

As you can imagine the cost is very minimal to always have your Pi conveniently available. The difference between the base cost and overclocking would probably be pennies a year depending on your applications needs, power saving modes, etc.

Conversely those same set of commands may be used for underclocking to reduce power consumption and heat by trading off reductions in performance. As they say a penny saved is a penny earned...but I'm spending it on the convenience and time saved! :)

[IceChes1]

@quicksilver 1. I don't know why it's that way.

[DTEAM]

@Riverstorm

I agree with what you are saying.

However, Guarantee = safety factor in engineering. If I want to burn my Pi in 2 years instead of 20 and I want to approach S.F. to 1.0 by iteration because I want more from my machine, I do not see where the problem is. I saw a difference in the performance, that's the problem.

I think It's not a bad thing to explore It with knowingly and knowing the impacts.

Everyone has their opinion on the matter and that's fine like this.