Overclocked Raspberry Pi 4 performance

Just was saying to compare crunch times on the stock system and then again AFTER the intended configuration change crunch times to see if the change was beneficial or not.

Sorry for causing some confusion.  I was in a hurry and was just trying to shoot off a quick response.

I also should have mentioned that there can be task to task variations that could disguise any benefit from overclocking so it's not a good idea to pick a single random task completed on stock settings and compare it with a single random task after overclocking.  The best idea is to select substantial 'before' and 'after' groups (perhaps 30 - 50 tasks each - the more the merrier) and work out the mean crunch time for each.  Looking at the individual variations within a group will guide you on how many tasks to choose for a reliable average time.

It can happen that factors other than raw frequency can limit the effect so there may not be as big a benefit as you might expect.  Care is needed so as not to cause bad results or to risk any damage to the device itself - eg. excess heat from greater power consumption.  I tend to think the downsides tend to outweigh the (usually) minor benefits from overclocking.

If you go to your account page on the website, it shows you a list of your computers.  If you have more than the small number listed, you can use a 'MORE' link at the bottom which leads you to a full summary list.

In the full list, for each computer there are more links - things like 'Details', 'Tasks', as well as a 'Last contact' link, all of which can be explored to reveal useful information.  You should try it out sometime - lots of interesting stuff to find.  If you follow the Tasks link, you get to see your full set of results categorised - ie. columns for things like 'In progress', 'Pending', 'Valid', 'Invalid', 'Error'.

When you look at your tasks, just be aware that they don't last all that long in the online database (maybe a week or a bit more if your quorum partner is slow) so if you want to note details like cpu time and run time, you should do so reasonably promptly.

I tend to call the run time the "crunch" time - its the full elapsed time that crunching lasted before the task was finished.  It will always be a bit longer than the actual cpu time because the cpu core doing the crunching may well be diverted to other higher priority jobs from time to time.  If you see a big difference between cpu time and run time, it's an indication that your device is heavily loaded - doing lots of other higher priority things which require large amounts of cpu time.

If you're definitely not running other compute intensive stuff while crunching, but you see a big difference anyway, perhaps you should investigate what is using all that time.  I haven't browsed any of your results so I'm not saying it's happening to you.  It's just something I tend to check on my own results if performance is not as expected.