Winging a Pi 3 overclock

[Nickcn]

deleted

[GTR2Fan]

Yep. Anyway, it's gone 1AM here so I'll bid you good night and toddle off to bed.

I think we can gloat in the glory that you may have had one of the fastest Pi3Bs on the planet at least for a little while today. No doubt others will be following suit pretty quickly, assuming that they haven't beaten us to it already.

[dukla2000]

Booted fine, but for some reason, it killed my wifi.

Code: Select all

# Uncomment to run sdhost overclock overlay and run high-speed sdcard at 100 MHz, and double read/write performance
#dtoverlay=sdhost,overclock_50=100

See this thread viewtopic.php?f=28&t=138542

[Nickcn]

deleted

[GTR2Fan]

Wow! It's nice to know that the guys are on top of a fix for this on the Pi3B already. Excellent work!

This script will tell you what speed the slot is being clocked at and what performance you're getting...

http://www.nmacleod.com/public/sdbench.sh

Copy the text then open a terminal and type...

Code: Select all

sudo nano sdbench.sh

...and paste the text in, then save with Ctrl-X, Y, Enter.

Make it executable with...

Code: Select all

sudo chmod +x sdbench.sh

...then run it with...

Code: Select all

sudo ./sdbench.sh

The 42MB/s read figure in my sig was taken from results from running the above script.

The recommendation is (or at least was) to use force_turbo=1 for best performance, but using core_freq=500 as you are which drops back to 250MHz when idle means that the dividers play nicely and the difference between forced and not forced is actually quite small and knocks a few degrees off your running temperatures.

[Nickcn]

deleted

[GTR2Fan]

Awesome! thanks. here are my results (btw, 10 loops on memtester all passed).

My pleasure. That's good news, and the microSD benchmark figures look pretty good too. Congratulations on now having one of the fastest Pi3Bs on the planet!

I can't remember whether I've given you this handy one-liner before or not, but running...

Code: Select all

while true; do vcgencmd measure_temp && vcgencmd measure_clock arm; sleep 2; done

...in a terminal while stressing the Pi (Quake 3 Arena! Cough! Cough! ) will tell you how hot the internal sensor thinks it is as well as showing you the CPU clock speed so you can tell whether or not it's backing off the CPU clock due to thermal-throttling.

[jahboater]

Have a look at bcmstat.sh as well.
https://raw.githubusercontent.com/Milho ... bcmstat.sh
Lots of info and in colour too.

[Nickcn]

deleted

[GTR2Fan]

I am already using the native internal raspbarian jessie pi3 apps for thermal core temp, and CPU use %, will those not suffice?

If they provide you with a log you can trundle back through to check recent historical values, yes. You won't be able to see the ones in the desktop taskbar if you go fullscreen 3D for GPU stress testing.

[Nickcn]

deleted

[GTR2Fan]

Yep. Either my one-liner or millhouse's excellent bcmstat will be required if the desktop isn't going to be visible.

[Nickcn]

deleted

[Trixster]

That's pretty good and you're unlikely to get anything discernible out of trying to push higher. I guess I'm just lucky with two rpi3s that will hit 600.

[karussell]

I've signed up just to say thanks for sharing your overclocking settings.

This is what I have running on my Pi 3 and it's as fast if not faster than my desktop PC running Kodi.

# uncomment to overclock the arm. 1200 MHz is the default.
arm_freq=1300
core_freq=500
over_voltage=4

# uncomment to overclock memory. 400 Mhz is standard.
sdram_freq=500
sdram_schmoo=0x02000020
over_voltage_sdram_p=6
over_voltage_sdram_i=4
over_voltage_sdram_c=4

# Uncomment to overclock the GPU
core_freq=500
v3d_freq=500
h264_freq=333

# Memory allocation of 1024MB for graphics processor
gpu_mem=256

# Uncomment to run high-speed sdcard overclock at 100 MHz, and double read/write performance
#dtparam=sd_overclock=100
dtoverlay=sdtweak,overclock_50=100


I still can't play x265 but that must be round the corner as when trying the cores aren't maxed out.

[Nickcn]

deleted

[karussell]

I hadn't spotted that. I've changed it.

Thank you.

[Dragoj]

hy ! i just buy RPI 3 with Kingston 64GB microSDHC/SDXC UHS-I U3 90R/80W and i want to play movies online with quasar , files over 15 GB high bitrate with hd sound , can someone help me with overclock ?

[Nickcn]

deleted

[JimmyN]

The best overclock I've gotten so far is 1372. It's stable at that speed running cpuburn-a53.

Here is the output from bcmstat.sh. This was taken at 3:45pm yesterday, so cpuburn had been running about two hours when I grabbed this from the Putty screen and saved it.

Code: Select all

Time         ARM    Core    H264 Core Temp (Max)  IRQ/s     RX B/s     TX B/s
======== ======= ======= ======= =============== ====== ========== ==========
15:48:35 1371Mhz  588Mhz  588Mhz 53.69C (53.69C)    264        147        451
15:48:38 1372Mhz  587Mhz  588Mhz 53.69C (53.69C)    270         22        125
15:48:40 1372Mhz  588Mhz  588Mhz 53.69C (53.69C)    273        102        285
15:48:42 1372Mhz  588Mhz  588Mhz 54.77C (54.77C)    263        367        285
15:48:44 1372Mhz  587Mhz  588Mhz 54.23C (54.77C)    287        762        125
15:48:46 1372Mhz  588Mhz  588Mhz 54.77C (54.77C)    274        124        285
15:48:48 1371Mhz  587Mhz  588Mhz 54.77C (54.77C)    262        103        288
15:48:50 1372Mhz  588Mhz  588Mhz 54.23C (54.77C)    272        139        214
15:48:52 1372Mhz  588Mhz  588Mhz 54.23C (54.77C)    273        102        285
15:48:54 1372Mhz  588Mhz  588Mhz 54.77C (54.77C)    289        775        334
15:48:56 1372Mhz  588Mhz  588Mhz 54.23C (54.77C)    258         22        125
15:48:58 1372Mhz  588Mhz  588Mhz 55.31C (55.31C)    274        102        285
15:49:00 1372Mhz  588Mhz  587Mhz 54.77C (55.31C)    273        102        285
15:49:02 1372Mhz  588Mhz  588Mhz 55.31C (55.31C)    258         22        125
15:49:04 1372Mhz  588Mhz  588Mhz 55.84C (55.84C)    289        827        288
15:49:06 1372Mhz  588Mhz  588Mhz 55.31C (55.84C)    278        282        310
15:49:08 1372Mhz  588Mhz  588Mhz 55.84C (55.84C)    261        102        285
15:49:10 1372Mhz  588Mhz  588Mhz 55.84C (55.84C)    270         22        125
15:49:12 1372Mhz  588Mhz  588Mhz 56.38C (56.38C)    282        826      1,871
15:49:14 1371Mhz  588Mhz  588Mhz 55.84C (56.38C)    277        820        285
15:49:16 1372Mhz  588Mhz  588Mhz 55.31C (56.38C)    271        254        125
15:49:18 1372Mhz  588Mhz  588Mhz 55.84C (56.38C)    274        139        335
15:49:21 1372Mhz  588Mhz  588Mhz 56.38C (56.38C)    264        178        388
15:49:23 1372Mhz  588Mhz  588Mhz 55.84C (56.38C)    274        215        150

Top shows

Code: Select all

 1628 jimmy     20   0    1680    332    276 R 100.0  0.0   2:53.72 cpuburn
 1629 jimmy     20   0    1680     84     16 R 100.0  0.0   2:53.84 cpuburn
 1630 jimmy     20   0    1680     84     16 R  99.7  0.0   2:53.58 cpuburn
 1631 jimmy     20   0    1680     88     16 R  99.7  0.0   2:53.45 cpuburn

This is what I'm using in config.txt

Code: Select all

gpu_mem=128

arm_freq=1372
over_voltage=5
gpu_freq=588

sdram_freq=588
sdram_schmoo=0x02000020
over_voltage_sdram_p=6
over_voltage_sdram_i=4
over_voltage_sdram_c=4

#SDCard overclock
#dtparam=sd_overclock=100
#dtoverlay=sdtweak,overclock_50=100

Those settings of course won't work for everyone, you may need to decrease a little, or possibly you could increase it a little, each RPi will be different.

You will need to have good cooling to run cpuburn at those settings, or you won't get far and it will start throttling back. I have a "tall" heatsink secured on with Artic thermal adhesive, I think it's "Artic Alumina". While running cpuburn I also have a 6" desk fan aimed at it to increase airflow. Without the fan the temp when running cpuburn will eventually get to 80C and it will start throttling back, which negates the overclock testing. So I aimed the fan at it and that lowered the highest temp almost ~25C by having air moving over it. The fan is only needed when stressing it with cpuburn, I've been using it for more than a day now and the temp hasn't gotten above 65C with just the heatsink and "normal" use.

Those settings seem to survive cpuburn for hours, and 4 loops of memtester twice, so now I'm checking to see how it does in the "real" world. It's definitely much faster, even with an update/upgrade/install using apt-get the speed difference is noticeable, with the only delay being during the download.