Benchmarking Raspberry Pi 2

If you follow us on Twitter, you’ll notice that I put a call out earlier today for people who’d benchmarked their Raspberry Pi 2 – I wanted to be able to share some benchmarking results with you this afternoon.

(Get well soon, Martin!)

Our old friend Dave Hunt (click on that link – it’ll take you to some of Dave’s projects, which are among the most beautiful we’ve seen made with a Raspberry Pi) has done some thorough benchmarking against a range of other devices. Click on the table to learn more and to see some very illuminating graphs.


The good folks at Adafruit have also been busy benchmarking, this time against the B+, and they also found themselves coming up with some really impressive results (a 7x improvement in some cases); click on the image to learn more.

Screen Shot 2015-02-05 at 14.58.13

Finally, here’s a really nice side-by-side comparison of the browser experience of the old B+ and a shiny new Pi 2. I recognise that second website Marco Barisione visits.



I wish to complain about the 2B as my coffee consumption is taking a hit because you’ve made it too fast. I used to be able to brew 20fl.oz. of coffee in the time it took to compile GnuCOBOL as it’s normally take about 16 to 18 minutes to rebuild from scratch & perform all the unittests Now it takes between about 5 minutes. and even less if i only do recheck of the unittests. That really isn’t enough time to a fresh coffee and i haven’t been able to make a sandwich to go with it in days.

PLEASE make all future models much slower please. my caffeine levels are plummetting


Are you making coffee with the Pi? Where’s the project?


Coffee and Pi….mmmmm!


How much USB current will I need to boil the coffee ? :)


Isn’t there a project where someone made a coffee maker out of a rpi?


You should use Emacs


Thank you. I am nearly mended…


Scratch benchmarks are not so optimistic. Some tests even run slower than on ModelB. See

From there:
Results, the smaller the numbers the better; left is B, right is 2B

move2 16.5 –> 13.7
rotate_say 9.3 –> 6.7

pingpong 8.4 –> 11.2
pingpong_remote 8.4 –>12.1

Strange. On one side there are 17 to 28% improvement; on other tests it runs 33 to 44% slower.


That’s very strange – that’s not what we’ve been seeing. We’ll get someone to have a look.


The tests where I notice improvements are very graphic-oriented.
The tests being slower are background ‘broadcast’ related.

This is all based on nuscratch from the current raspbian distribution. Think the squeak underlying is possibly overspecialized for Model B??


There is nothing in NuScratch that is ‘over specialized for the model B’. The broadcasts are done via perfectly normal socket APIs, so any change in performance there will be down to lower level changes. I’m sure we’ll find out soon.


This ‘slow test’ is a complete internal ‘broadcast’ test, no scratch sensor network involved. Of course I did another test involving remote socket connections, showing similiar results. Looks as if scratch internal broadcast system is affected. I’ll post the code in the the forum.
Regards, Gerhard



I wrote a (unfinished) demo that renders Mandelbrots using GPU shaders, where the CPU only provides coordinates and plays some music. That one also runs slower compared to the B(512MB).



That’s interesting; I’d expect it to be the same speed, not slower (the added performance comes from the extra CPU cores, so GPU exercises should be like-for-like).


Are you sure you are not stalling waiting on responses for expected time/duration of work? If the procedure (for example) takes 10ms and the pi2 is working in 6ms, but stalls for 18 to catch up to when you expect a response?


I haven’t created any complicated code within Scratch, but if nothing else the Scratch user interface is much faster. I ran a 10 week CodeClub running Scratch on the original Raspberry Pi and whilst usable I did have to tell the children to be patient when there was a delay between them clicking and Scratch responding.

I ran Scratch on my Pi 2 and my son’s Pi B+ and there was a noticeable delay in response from the GUI when creating a program on the old B+, but it was pretty much instant on the Pi 2. This is a big improvement and makes the Raspberry Pi much better.

Both were running the latest NOOB image.


Transcoding Skinny Puppy’s “Pro-Test”, 360×270 Quicktime .MOV, 256kbps MP3, to same resolution MP4 at CRF 26, 96kbps, using avconv:

Raspberry Pi 1 (1x 700MHz ARMv6, 512MB RAM, Raspbian Wheezy): Average 1 frame per second. 18 mins to complete.

Raspberry Pi 2 (4x 900MHz ARMv7, 1GB RAM, Raspbian Wheezy): 28 FPS, 4 min 9 secs to complete –

Intel Celeron dual-core (2x 2.5GHz 686, 2GB RAM, Ubuntu Precise): 114 FPS, 1 min 3 secs

This has interesting ramifications for the Foundation’s stop-frame animation tutorial I’m planning for Cotswold Raspberry Jam (next event probably Sat 18 April). When my daughter Annabel did the stop-frame tutorial at Pycon, time limitations of the Jam required her to use Ben’s Intel laptop to render the .JPG frames into a video file, because the Pi 1 would take about 2 minutes per frame to render – it wouldn’t have been finished by the time the Jam finished. With the Pi 2’s performance, it looks like this will be practical to render on the Pi 2 itself, live during the event.


Do you have a copy of that video file? Or can you repeat the test on a Pi2 with a freely available video please?

I’ve got a HP N36L Microserver I do transcoding on and I’m actually wondering if using the Pi2 is going to be faster, so I’d like to compare the speeds.


Okay, using the Big Buck Bunny trailer, 480p, transcode from Quicktime to h.264, 128kbps AAC.

Pi1: 63 mins 25 secs (<1 fps)
Pi2: 1 min 19 secs (10 fps)

sudo service lightdm stop
sudo apt-get install libavcodec-extra-54 libav-tools
wget ";
time avconv -i -vcodec libx264 -preset fast -crf 26 -strict experimental -acodec aac -b:a 128k output.mp4

Raspberry Pi 1 Model B (512MB RAM, gpu_mem=128)
real 63m25.871s
user 32m54.970s
sys 0m10.980s

Raspberry Pi 2 Model B (1GB RAM, gpu_mem=128)
real 1m19.191s
user 4m32.910s
sys 0m1.980s


Actually, repeating the sysbench tests show that the N36L is still about 7x faster still than the Pi2, so I’m guessing ffmpeg is going to be slower. Oh well! Still can’t wait to receive my new Pi!


I recompiled x264 for cortex-a7/NEON and got a 30x improvement in sped over the Pi1. I would expect similar improvements for other codecs, if they use NEON.


This is really a desktop machine now .. just amazing! the browser is so usable …
I ran the wolfram mark system comparison …had some licensing issues at first but then rebooted and it finally worked .. this is from the jan 2015 raspian distro..
raspberrypi2 0.05
Linux ARM (32-bit)

ARMv6-compatible processor rev 7 (v6l) 0.01
Linux ARM (32-bit)

=== WolframMark Detailed Timings ===

Total Test 1 Test 2 \

> Test 3 Test 4 Test 5 Test 6 Test 7 Test 8 Test 9 Test 10 \

> Test 11 Test 12 Test 13 Test 14 Test 15

Intel Core i7-3770 CPU @ 3.40GHz (8 cores)
Linux x86 (64-bit) 7.3 0.38 0.31 \

> 0.48 0.42 0.62 0.41 0.40 0.68 0.40 0.75 \

> 0.64 0.09 0.85 0.45 0.45

3.5 GHz 6-Core Intel Xeon E5
Mac OS X x86 (64-bit) 7.4 0.61 0.36 \

> 0.28 0.45 0.30 0.47 0.43 0.99 0.29 0.67 \

> 0.69 0.09 0.89 0.43 0.42

Intel(R) Core(TM) i5-3550 CPU @ 3.30GHz
Microsoft Windows (64-bit) 8.3 0.47 0.34 \

> 0.48 0.53 0.80 0.45 0.47 0.63 0.44 0.86 \

> 0.69 0.11 1.00 0.55 0.53

2.2 GHz Intel Core i7
Mac OS X x86 (64-bit) 11.5 0.84 0.47 \

> 0.49 0.68 0.83 0.58 0.53 1.64 0.73 0.82 \

> 0.92 0.12 1.20 0.88 0.75

3.07 GHz Core i7-950 (8 Cores)
Windows 7 Pro (64-bit) Desktop 13.8 0.80 0.98 \

> 1.00 0.80 0.84 1.00 0.98 1.00 0.78 1.06 \

> 0.95 0.89 0.97 0.92 0.86

2.93 GHz Core i7-940 (8 Cores)
Linux Ubuntu (64-bit) Desktop 15.6 0.94 0.99 \

> 1.14 0.92 0.80 0.81 0.88 1.51 0.89 1.31 \

> 1.16 1.14 1.41 0.89 0.86

Intel Core i7 CPU
Microsoft Windows (64-bit) 16.5 0.93 0.72 \

> 0.68 1.23 1.44 0.89 0.85 1.02 1.40 1.33 \

> 1.58 0.15 1.44 1.47 1.33

2 × 2.26 GHz Quad Core Xeon E5520 (8 Cores)
Mac XServe OS X (64-bit) Server 20.1 1.06 1.22 \

> 1.44 1.00 1.67 1.05 1.12 1.71 0.67 2.79 \

> 1.32 1.22 1.76 0.94 1.08

2.80 GHz Core 2 Duo Mobile T9600 (2 Cores)
Windows 7 Pro (64-bit) Laptop 20.7 1.12 1.20 \

> 1.90 1.06 2.04 1.17 1.15 1.61 1.53 1.61 \

> 1.19 1.06 1.22 1.25 1.56

2.4 Ghz Core 2 Duo Mobile T8300 (2 Cores)
MacBook OS X Snow Leopard (64-bit) Laptop 29.8 1.78 1.40 \

> 2.44 1.40 3.03 1.13 1.22 2.20 2.35 2.31 \

> 1.63 1.57 2.06 2.86 2.38

2.60 GHz Core 2 Duo Mobile T7800 (2 Cores)
Windows XP Pro (32-bit) Laptop 31.8 1.27 1.80 \

> 2.59 1.44 3.69 1.92 2.06 2.41 3.25 1.91 \

> 1.45 1.41 1.34 2.52 2.72

2.13 GHz Core 2 Duo E6400 (2 Cores)
Windows Vista (32-bit) Server 38.1 2.49 2.18 \

> 3.39 1.75 3.18 2.35 2.54 2.92 3.28 2.52 \

> 2.33 1.65 1.78 3.12 2.60

1.6 GHz Core 2 Duo Mobile L7500 (2 Cores)
Windows 7 Pro (32-bit) Laptop 43.8 2.17 2.75 \

> 3.74 2.26 4.23 2.90 3.14 3.46 3.42 2.73 \

> 2.48 1.92 2.11 3.39 3.12

2 × 2.00 GHz G5 PowerPC (2 Cores)
Mac OS X (32-bit) Desktop 100.9 4.61 4.64 \

> 10.91 4.94 19.50 5.16 5.01 5.70 5.21 7.17 \

> 3.33 4.87 4.28 9.74 5.84

Linux ARM (32-bit) 307.6 14.04 5.43 \

> 35.62 25.71 26.06 7.19 7.65 6.89 55.10 8.58 \

> 13.40 0.99 9.53 44.82 46.55

ARMv6-compatible processor rev 7 (v6l)
Linux ARM (32-bit) 3011.0 31.84 15.55 \

> 84.43 144.50 183.10 16.49 20.02 28.88 1165.00 37.60 \

> 36.45 4.70 25.73 444.20 772.60

(Timings are CPU time in seconds)
just amazing the difference ..


Looking at the Mathematica benchmark’s it appears for some tests, such as test 9, that the pi2 is 21 times faster. The is the kind of speed up one would expect between software float and hardware float. Is it possible Mathematica on the original PI is not making use of hardware float? Alternatively this could be a low memory swap issue. Any idea which? The memory issue can’t be fixed, but hardware float on the original PI is certainly possible.


Since some people have stated that this new version of the Pi migh be adequate as a replacement for a desktop system for those who can’t afford one it would be interesting to see a comparison (as crazy as that might appear) between the Pi2 and say a Pentium 4, C2D, Core Quad, both in benchmarks and real life usage (word processing, spreadsheets, photo editing) – no expectations here, just curiosity. I’d do the comparisons myself, but I don’t have a Core Quad based Pc. And it’ll be long before I get a Pi2 (unless someone wants to donate lne to science


Wow, that was fast. The tests were ready before I finished my post! Must the the 4 cores… ;)


Very preliminary results from last night showed that compiling FFTW3 on a PI2 with and without the NEON SIMD extension produced a 25% improvement in FFT speed. Tests agains PI1 this evening.


Compiling OpenCV 2.4.10 in 34 minutes on the Pi2 is quite an improvement compared to 10 hours on the Pi1 .


I was going to ask about OpenCV. That’s an amazing improvement, I assume that it improves things for the operation of OpenCV a as well. It’ll be really awesome to improve the vision analyses abilities and have more robotic eyes!


I’m guessing that big speedups in compiling large projects has something to do with memory size, as well as the CPU. If you have to use a swap file on flash due to 512MB memory limit, it has a big impact.


May i ask you something? How did you achieve that time? I’ve compiled OpenCV 2.4.11 on Raspberry Pi 2 today and it took almost 6-7 hours! I’m a bit frustrated actually


I get 314 on my wonderful new RPi2. About 100xPi ;-)


Not really a benchmark, but OpenArena runs at a solid 60 fps on the new pi! Tremulous 1.0.2 too! Haven’t tried Quake3 yet but it should also play smooth as butter.
View in 1080p60 or 720p60 for best experience:


I’ve also try OpenArea and was amazed to see it running butter-smooth on the RPi 2. Well beyond my expectation, which was “hopefully slightly less jerky” .


Any power consumption comparrisons? Although completing tasks quicker probably requires more intense power consumption, is it more efficient overall? Has anyone pointed a thermal camera at Pi2?


Has anyone compared JVM performance between the two? In theory, the 4-cores should make a _huge_ difference in garbage collection performance if you use one of the concurrent collectors like G1.

(Does the JVM even run on the pi 2?)


Completely unscientific so far (playing around while i should have been getting ready for work this morning)…

Dosbox compiled with dynamic core for B+: Struggles to play wolfenstien 3D smoothly (286/early 386 era)

Dosbox compiled with dynamic core for 2B with neon: Wolf3d is smooth as butter and descent (late 486 era) has a reasonable frame rate.

Can’t wait to test more over the weekend


*cough* Dune II?

*envisages many sleepless nights*

I may, or may not, have discovered the wonderessness of time mismanagement for resources when playing this game at university. Especially on the ‘Oh, it will be a quick game’ at 9PM, and I’m still playing at 6am….


Heh, ditto ;-)


2B or Not 2B. that is the question :P


Hackaday also just published bunch of benchmarks:


I’m still waiting. It’s expected next monday.

So the only benchmarking I can do is comparing how long it took to get an original Pi versus how long it’s taking to get a Pi 2. So far the Pi2 is about 12x faster at getting from launch to my front door. Impressive improvement




We were talking about this last night: in terms of how long it took us to build and ship the original 2012 batch, we’re already up to July on day five!


Got My Pi2 tonight … LOVE it! But … Worth mentioning that much of the software/distros are in alpha or beta so that although Pi2 is MUCH faster it’s a little less stable than the B+ which is pretty rock solid. .. openelec I’m testing is only 2 days old … Great Pi which will get greater with development! Thankyou!!!


I´d really like to know if there´s a big difference when using Openelec. I´ve been using it for some weeks now on a B+ without overclocking and it feels fast enough – I don´t have a huge video library I must say, all I do is watch some videos stored on an external HD and some stuff off youtube, so the GUI for me is pretty responsive, but maybe if I had a bigger library the B+ “limitations” would appear more obvious.


There’s a VERY big difference in the responsiveness of the library; menus are like butter off a hot knife.


Hi Tzarls ! Actually I’ve been running Openelec since getting my first Pi (B 264mb ram) With no problems .. We use a B+ because of the four usb ports not because the old pi struggled. I’m hoping the Pi2 will be able to handle more plugins and addons I’m testing OpenELEC-RPi2.arm-5.0.1.img .. the Wireless Networking seams a little aggressive/fast/glitchy? but aside from that .. Ram usage is around 9% the cores arent even trying … installing addons is now instant. rss feeds are smooth as silk .. I’ll try some more tests tomorrow! (I’m not planning to replace my B+ yet!) pete


Just read this on the openelec site ..

You can now provide up to 1.2 Amp to the USB ports – enabling you to connect more power hungry USB devices directly to the Raspberry PI. (This feature requires a 2Amp micro USB Power Supply)

Is that a Pi2 thing or was this possible with a B+?


That change was introduced on the B+.


Openelec – Boot time
B+ 39sec
Pi2 16sec


Openelec Install Youtube add-on
B+ 9sec
Pi2 2sec

Using the add-on is MUCH slicker on Pi2 with very reduced wait times.


openelec boot times and add-on install times are almost the same on my A+ compared to my B+ … The size of ram doesn’t seem to worry OE .. The processor seems to be the important factor.


Grrr. I’m waiting impatiently for mine, ordered 2/3/2015


I am noticing a big difference on emulation like the Amiga and Super Nintendo. Now they run smooth and there is not a stutter in sight. This is great work for anyone who wants to make a gaming cab and what a small form factor with low power.


Our STEM club were well chuffed with the Pi, and set up a quick, if arbitrary benchmark within minecraft using 5x5x5 cube of TNT. We recorded a youtube video of a Pi2 and a B+ side by side.
Result: The Pi B+ is roughly twice as fast to calculate the effect of the explosion of the TNT block!


Maybe I am overlooking something. But no one in the tests above (at least the video render or minecraft) examples say what kind of storrage is attached.

I hope all those tests use card which habe been checked with a benching tool verifying identical read / write speeds.


I would be interested in comparisons with classic mainframes/supercomputers/workstations:

How does the Raspi 2 compare to a Cray 2? Vax 11/780? SGI Origin (or O2)? Sparcstation 20?


Taking each in turn…

The strength of the Cray was in floating point performance, hitting 1.9GFLOPS. The GPU in the original 700MHz Pi was clocked at 24GFLOPS. But ignoring the GPU, the ARM core at 900MHz should run to at least 0.05 GFLOPS, and you’ve got four of those in a Pi2, running to 0.2 GFLOPS with a trailing wind. To beat the Cray you’d need an array of a dozen Pi’s which would set you back over $500 – but that’s a lot less than the $16 million you’d need for a Cray-2 in 1985; and back then, $16 million was a lot of money.

The Cray did look awesome though.

VAX-11/780 was the engineer’s choice of minicomputer – much like the Pi today perhaps. However with only a single 5MHz CPU and a maximum of 8MB RAM (that’s MegaByte, not GigaByte, kids) I think the Pi would run rings around the old beast. The VAX would win if it was a sumo competition of course – the CPU cabinets alone weigh in around a metric tonne.

SGI were sold as graphics workstations but I suspect that by today’s standards even their highly-tuned graphics subsystems would be outperformed by the GPU in the Pi. The baby O2 (single 400MHz CPU and 1GB RAM) wouldn’t scare the Pi2 but the bigger Octanes with dual 600MHz MIPS processors and 8GB RAM might give the Pi a black eye. But side-by-side? the graphics on the Pi would outshine what were the best of the 1990’s desktops.

The SPARCstation 20 seemed great at the time. It could support quad RISC processors, but only at 200MHz, so round 1 to the Pi2. Maximum memory? 512MB. Round 2, Pi2. Built-in Ethernet? 10Mbps only. Round 3, Pi2. Graphics? Knockout blow by the Pi2. With a full spec SS20 costing well over $20k back in 1995, it’s an easy win for Raspberry Pi.

Computing is an area where the products get old, fast. I have a collection of old machines (including small VAXen and SPARC hardware) but it’s hardly worth the electricity to turn them on nowadays. They deserve to be preserved as they are part of our journey but we have come a long, long way in one human lifetime.

My first computing experience was playing Lunar Lander on the GT40 front-end processor of a DECsystem-10 in about 1975. I can’t begin to guess how much that configuration cost! Anyways, if the Pi can deliver the same magical experience to a whole generation of budding computer scientists, programmers and designers then I’d say the Pi wins hands down.


You owned a VAX? I’m impressed. I owned a PDP-11/03. Lovely machine. It was actually a Heathkit H11 and I assembled the power supply, backplane and case myself. The architecture was so simple that you could program it in assembler and feel like you were doing magic. An emulator on the Pi would run many times faster than the real thing. 64k of RAM fully stacked (for an outrageous amount of moolah), and I had 2 x DSD440 (RX-02 lookalike) disk drives for a whole 1Mb of floppy disk! Those were the days.


I would like to see the I/O system benchmarked. How limited is the combined USB-Ethernet bus?

Early benchmarks
1) On the hard drive side, running hdparm -t /dev/sda1, and getting almost exactly 30MB/s or 240Mb/s !!!
2) On the network side, the internal 100Mb/s Ethernet has already maxed out at greater than 90Mb/s speeds.

Benchmarks that I would like to see:

One way bandwidth
1) dd a large file on a fast USB flash drive, to /dev/null, and time it.
2) Connect a USB Gigabit LAN adapter to the RPi2, and connect the LAN to a PC. Run iperf on both the PC and RPi2.

1) dd a file on a fast USB flash drive, to another fast flash drive.
2) Install 2 USB Gigabit LAN adapters on the RPi2, and setup a network bridge between them. Connect the LAN to two PCs, and run iperf on both PCs.
3) Setup a Samba share using a fast USB flash drive through a USB Gigabit LAN adapter.


Buy one! You can easily do those tests.


I’ve got the Amazon gift cards just waiting for them to drop below $70.


The Einstein@Home benchmarks are a bit confusing and/or disappointing. The Pi 2 comes up only a tad faster than the Pi 1 (basically about the ratio of the clock frequencies). This could be because they are per-core benchmarks, in which case I should get 4+ times the throughput in the long run, or it could be because the cores are sharing the integer and floating poiint units (which would seem a bit pointless). I haven’t yet done enough E@H work on the Pi 2 to get a throughput score. It will take a day or two. I’ll post an update when the picture is clearer.


Is it possible to overclock Raspberry Pi 2? How much range could I got to overclock it? I’ve a RPi 1B and I overclocks it to 800MHz.


I tried a very unscientific test of running my version of Life. It calculates an area of 704 X 450 and wraps at the edges, I did a timing run for 9000 generations.
Both Pies were set to the came cpu, core and clock speeds, with no X running, and as far as I’m aware only a single CPU was used on the Pi 2.
On a Raspberry Pi B it completes 9000 generations in 20 seconds.
On a Raspberry Pi 2 it completes 9000 generations in 7 seconds!
This seems surprisingly good as it’s exactly the same code, which I had optimised as much as I could, with exactly the same CPU frequencies, I can only think that because of the larger internal cache, the whole of the program plus array storage can fit in the Pi 2 cache and it couldn’t in the Pi B. Obviously it still has to slow down to do the screen updates, which presumably will have to be in main memory.
While I’m on the subject, I used ‘cc -O2 life.c’ to compile this, can anyone tell me if there are any better options I can use for the Pi 2 as it’s an ARM 7?
Thanks, Kevin Moore.


has anyone done a test with openssl? the command is

$ openssl speed

I did a quick and dirty test and it only seemed to use one core. Is it compiled with multithreaded options?


Guys – I have very slow video playback (tested on Buck Bunny 1080p) on rpi2 using both openelec and OSMC. About 10 fps with acceleration on (cores about 10-15% of load and 0% of vpu), when I switch off acceleration fps drops even lower (more cpu usage, and no vpu load). Any ideas?


That’s definitely not right. Have you updated your firmware?


Liz, what you mean by updating firmware?
I’m using most fresh available release of OSMC (alpha 4) and openelec 5.0.1


Did a benchmark of the rupy cometstream and 6x it is. Almost the same performance as an old atom or a new NUC, but per watt it dominates!


I would have jumped at getting one already, but it’s just a small bored with everything on it, and i don’t have the tools needed to make a casing for it, i wish i did.. but i don’t.
REALLY wish i had a 3D printer.


A quick google search will show you that there are dozens of 3rd-party cases available to buy for the Raspberry Pi. Thanks to the same form-factor (almost) every case for the Pi B+ will also fit the Pi 2.


I’ll probably get laughed off the comments for posting this (because it’s not exactly a benchmark) but I remember Fibrelamp on xscreensaver when the Pi launched – probably one frame every 3 seconds; it’s performance gradually increased with all the hard work you guys did with code / OS optimisation over the R-Pi-1 era. It will come as no surprise to hear it’s all Kerry Gold in the frame-rate department on R-Pi-2. :-)

Seriously though, the Raspberry Pi 2 is *utterly butterly* – this machine is a game changer for you and Planet Earth and I just know that you’re going to sell zillions of them! :-) I can’t wait to see how it evolves in hard/soft-ware over time … congratulations to everyone on the R-Pi team! :-)


Got my Pi2 on Saturday and did this test:
1) Created a simple python script to calculate the first 50 Fibonacci numbers. I do this 1000 times and then print out the average duration of the 50 calculations.
2) I then loaded this script onto my B+ and my Pi2
3) Opened up 4 SSH shells into each of the above RPIs and launched the script from the command line
4) Observed that the B+ calculation time got slower and slower as I added SSH sessions while the Pi2 seemed unaffected.
5) Final values: B+ .00844, Pi2 .00138 -> 4:53:1 performance improvement for the Pi2.
6) Note that when I added a fifth SSH session to the Pi2 and ran the script, the timings finally took a hit. So I think it’s safe to say that those four cores make a difference.

Way to go, guys!


I’ve posted a detailed comment on the forum about the performance improvement I noticed when using a testbench for an in-memory database – see Basically, without any recompilation or over-clocking, I saw 4-fold performance improvement for single-threaded sets, and 6 to 8 times better when using multiple connections to the server.


Anyone cares to run a quick and dirty bc benchmark
time echo "scale=5000; a(1)*4" | bc -l"
for the delight of the rest of us who don’t own a RPi 2 yet?


Running time echo “scale=5000; a(1)*4” | bc -l:

real 2m39.215s
user 2m38.580s
sys 0m0.050s

That’s on a PI2 which is doing a bunch of other stuff (the only one I have at the moment.)


Well the CPU performance is nice: but I guess there is a problem with the GPIOs. Using file system IO access is approx 20 times slower than on my RPi1 models. And trying to access /dev/mem simply ends in a memory exception, The pigpio and other libraries show similar problems…


I ran a python script that converts a set of Excel spread sheets into an sqlite database (uses the xlrd and sqlite3 modules). Elapsed time:
Raspberry Pi : 211.7 seconds
Raspberry Pi2: 44.0 seconds
Core i5-2500K: 5.76 seconds

So the Pi2 was about 4.8x faster than the Pi, but there is still a big gap to the desktop computer. The two Pi’s were not using the same SD card, but I think most of the difference is CPU rather than ‘disk’ performance.
Python2 ran from the IDLE. No multi-threading in the script.


I should have said that the old Raspberry Pi was a model B with 512 MB of RAM. When I repeated the test on the Pi using the same memory card as the Pi2 had used, the elapsed time was 202.5 seconds reducing the Pi2 to 4.6x the Pi.

Here are some selected openssl speed results. I’ll limit the results to sha1, aes-128 cbc and rsa1024
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 1891.80k 6231.80k 15700.76k 24939.09k 30267.47k
aes-128 cbc 13216.40k 15060.31k 15628.00k 15874.29k 15794.54k
sign verify sign/s verify/s
rsa 1024 bits 0.011186s 0.000633s 89.4 1579.4

type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 4328.63k 12399.76k 26505.19k 37364.43k 42440.55k
aes-128 cbc 18197.11k 20362.14k 21042.86k 21218.23k 21255.65k
sign verify sign/s verify/s
rsa 1024 bits 0.006949s 0.000387s 143.9 2584.5

These sample numbers numbers don’t favour the Pi2 as much. The ratio is between 1.34 and 2.28


Sounds like the tests are only using one core. In which case 1.3-2.2 sounds about right. With the right software running on 4 cores, I have seen code speed increase by x30 for x264 encode. So it is very dependant on what you are doing (which is why most benchmarks are not that important)


Here are a lot more benchmark results:

They are part of my Raspberry Pi 2 Model B review (published last night)


Hi everyone,

Could somebody take timelapse photos of the Pi camera on the Raspberry Pi 2 model B and give me the smallest number between 2 shots without the delay? In Raspberry Pi 1 mode l B+, I need at least 1.7s between 2 continuous shots.

Here’s the command?

raspistill -tl 1.7 -t 60000 -o image%04d.jpg

You can change 1.7 to 1.0 or 0.5

Thank you very much,

Best regards,


This question is better asked (and already answered?) on the forums.


I ran some more benchmarks.

Raspberry Pi 2: Raspbian vs. Linaro (ARMv6 vs ARMv7)


Here is the “Geekbench 2 for ARM” results comparison for the Raspberry Pi 2 vs HummingBoard-i2eX


my experience over model B+ and pi 2
i’ve used B+ before with my sdl2 program :
animation , bunch of texture and other think
B+ work well :5 to 7 fps quite good for me and my application.
Model pi 2 coming with a lot of improvement
so i think with pi 2 my program get well.
the same program run quite 7 times slow
i’ve noticed that program slow
with function that have to move lot memory
on the other side SDL_SetRenderDrawColor running faster
but i use lot of first function
question is how i run my program at least at same speed of previous B+
ps with overclock run little bit faster but not so much
advice and comment are welcome
(forgive my english)


This isn’t the right place for tech support – please post your question in the forums!


Please post on the forum for tech support.


When gzipping a file, I found the Pi 2 to be 3 times as fast as the Pi 1 (single-core), and about 8.3 times as fast using 4 cores.

When computing checksums of large files, the Pi2 is again 3 times faster than the Pi1, and over 15 times faster using 4 cores.

Results here


It would be nice to have some kind of standard benchmark for testing SD and microSD cards inside the Raspberry Pi itself. There are many methods around the net… we need a standard one so we can compare.


Has anyone run RISCOS Pi on the Raspberry Pi 2? I’d like to know what people think of it, vs. that OS running on the Raspberry Pi 1. How much more responsive is desktop performance (window moves as well as resizing, opening/closing, etc.) and other aspects, including Web Browsing?

Leave a Comment

Comments are closed