Benchmarking the Raspberry Pi 2

When I saw that the Raspberry Pi 2 had been launched earlier on this week, I immediately decided that I had to have one. My original Raspberry Pi had been slowly gathering dust on the study windowsill for a couple of years, largely because my initial enthusiasm for it had waned rather quickly. It was simply too slow and unresponsive for me to be able to do anything very interesting with it.

However, my experience so far with the RPi 2 is making me wonder why I bothered to buy a new PC towards the end of last year. For the princely sum of £29.93 (delivered) from CPC (plus an additional £16 for a 5V, 2.1A power supply – the 700mA phone charger that worked with my original model B simply wasn’t up to the job), it’s more than adequate for programming tasks.

The RPi 2 even runs a web browser sensibly, which is more than I ever really managed to achieve with my first RPi. (Geek note: this post was written on my RPi 2, using the Chromium browser).

But just how good is it? A number of people have been testing its performance by playing old computer games on emulators, but that seemed a little bit too subjective for my tastes.

So instead, I installed a FORTRAN compiler and dug out a copy of the double-precision Whetstone benchmarking program(+). An average of 10 runs over 100,000 loops each (on a single core of the quad-core ARM v7 processor of the RPi 2) gave me a result of 276,369 double Whetstone KIPS (thousands of instructions per second).

Double Precision Whetstone Benchmark Results, RPi 2

It’s only when you dig out the historical results for this benchmark(*) that you start to realise how astounding this performance figure is. For example, the VAX 11/750 that I used for the first time at Warwick University in 1982 delivered around 510 KIPS of performance and was typically shared by two dozen people at once. At particularly busy times you could wait for whole minutes simply for the text editor to start.

The Prime 9955 that was the mainstay of development work when I joined my first company, PAFEC, delivered 3,450 KIPS, according to its 1986 benchmark results. I still have my original contract of employment, which stated that staff who worked on “the computer” were encouraged to adopt some rather unusual working hours. The Silicon Graphics Indigo2, the workstation that everyone wanted to use in 1993 as it was a byword for high performance computing, clocked up a very respectable 90,000 KIPS.

It’s only when you get to the release of Pentium II based PCs in 1998 that you start to see similar performance figures to that of a single core of the RPi 2. And you need at least a Celeron M or Pentium IV based PC from 2003 or 2004 to match the performance across all four cores.

I suppose I really ought to knock the dust off my original RPi and see how it performs with the same code …

Update, 8th February 2015I’ve now repeated the benchmark on my original model B.

(+) The Whetstone benchmark seems particularly appropriate, as like the Raspberry Pi, it was created in the UK.

(*) I’m indebted to Roy Longbottom and his collection of benchmarks for the historical performance information referenced in this post. The documents covering the development of the Whetstone (and other benchmarks) he’s curated are a fascinating glimpse into one aspect of the history of computing over the last 60 years or so.

 

7 thoughts on “Benchmarking the Raspberry Pi 2

  1. Rapsberry pi 2 comparable to Pentium IV?!, now that’s an serious upgrade for that tiny machine. Thanks for the review.

  2. Kinda scary that the pi now has some much power. What kind of SD card did you use? My old Adata class 10 card runs terribly but I blame it, not my pi 2.

    1. A bog-standard class 10 8gb card. But for this benchmark it should make no difference at all, as memory usage is insignificant.

  3. Hmm… faster than a Prime/Vax 11/780…..FORTRAN compiler ….that means we just need a suitable graphics library and DOGS (The Drawing Office Graphics System we worked on at Pafec) would run on it!!

    1. I don’t see why not! And as the window manager is based on X, then that shouldn’t be too difficult to achieve either!

Your thoughts?