DEV Community

Mahinsha Nazeer
Mahinsha Nazeer

Posted on • Originally published at Medium on

Raspberry Pi 3 Model B Plus Rev 1.3 Overclocking Test

Overclocking is a popular technique among tech enthusiasts looking to push their hardware beyond its factory-set limits. This blog explores the potential of overclocking the Raspberry Pi 3B+, a versatile and affordable single-board computer beloved by hobbyists and professionals alike. I aim to unlock new capabilities and enhance efficiency by tweaking its clock speeds and optimising its performance.

Join me as I dive into the process, share our results, and provide insights into the benefits and challenges of overclocking the Raspberry Pi 3B+.

Raspberry Pi 3B+ Specs:

       _,met$$$$$gg. root@pi 
    ,g$$$$$$$$$$$$$$$P. --------- 
  ,g$$P" """Y$$.". OS: Debian GNU/Linux 12 (bookworm) aarch64 
 ,$$P' `$$$. Host: Raspberry Pi 3 Model B Plus Rev 1.3 
',$$P ,ggs. `$$b: Kernel: 6.6.31+rpt-rpi-v8 
`d$$' ,$P"' . $$$ Uptime: 1 hour, 37 mins 
 $$P d$' , $$P Packages: 1562 (dpkg) 
 $$: $$. - ,d$$' Shell: bash 5.2.15 
 $$; Y$b._ _,d$P' Resolution: 1024x768 
 Y$$. `.`"Y$$$$P"' CPU: (4) @ 1.400GHz 
 `$$b "-.__ Memory: 216MiB / 907MiB 
  `Y$$
   `Y$$.                                              
     `$$b.                                            
       `Y$$b.
          `"Y$b._
              `"""

  Model name: Cortex-A53
    Model: 4
    Thread(s) per core: 1
    Core(s) per cluster: 4
    Socket(s): -
    Cluster(s): 1
    Stepping: r0p4
    CPU(s) scaling MHz: 50%
    CPU max MHz: 1400.0000
    CPU min MHz: 600.0000
    BogoMIPS: 38.40
    Flags: fp asimd evtstrm crc32 cpuid

Enter fullscreen mode Exit fullscreen mode

I am currently utilizing a 5V high-performance cooling fan for my Raspberry Pi, without any heat sinks. For fan control, I have designed a custom transistor-based switching device that operates based on a Python program and the Raspberry Pi’s GPIO pins. However, for this particular experiment, I have bypassed the switching mechanism and configured the fan to run continuously in an “always-on” mode.

Stressberry Benchmark Output:

GPU:

CPU:

    Model: 4
    Thread(s) per core: 1
    Core(s) per cluster: 4
    Socket(s): -
    Cluster(s): 1
    Stepping: r0p4
    CPU(s) scaling MHz: 50%
    CPU max MHz: 1400.0000
    CPU min MHz: 600.0000
    BogoMIPS: 38.40
    Flags: fp asimd evtstrm crc32 cpuid
Enter fullscreen mode Exit fullscreen mode

New configuration:

arm_fr

Architecture: aarch64
  CPU op-mode(s): 32-bit, 64-bit
  Byte Order: Little Endian
CPU(s): 4
  On-line CPU(s) list: 0-3
Vendor ID: ARM
  Model name: Cortex-A53
    Model: 4
    Thread(s) per core: 1
    Core(s) per cluster: 4
    Socket(s): -
    Cluster(s): 1
    Stepping: r0p4
    CPU(s) scaling MHz: 100%
    CPU max MHz: 1800.0000
    CPU min MHz: 600.0000
    BogoMIPS: 38.40
    Flags: fp asimd evtstrm crc32 cpuid
Caches (sum of all):
  L1d: 128 KiB (4 instances)
  L1i: 128 KiB (4 instances)
  L2: 512 KiB (1 instance)
Vulnerabilities:
  Gather data sampling: Not affected
  Itlb multihit: Not affected
  L1tf: Not affected
  Mds: Not affected
  Meltdown: Not affected
  Mmio stale data: Not affected
  Reg file data sampling: Not affected
  Retbleed: Not affected
  Spec rstack overflow: Not affected
  Spec store bypass: Not affected
  Spectre v1: Mitigation; __user pointer sanitization
  Spectre v2: Not affected
  Srbds: Not affected
  Tsx async abort: Not affected
Enter fullscreen mode Exit fullscreen mode

Benchmark Results:

Top comments (0)