Benchmarking the GPIO pins on a Raspberry Pi | Zack Scholl


Benchmarking the GPIO pins on a Raspberry Pi

How fast can the GPIO pins read and write?

Benchmarking the GPIO pins

tldr; use Go for reading GPIO pins because its about as fast as C for practical uses and a bit easier to code in, but use C if you want to write to pins (max cycle rate 15 MHz) or if you just want to keep things in memory.

A good question to ask yourself before using the Raspberry Pi GPIO pins for time sensitive things is exactly how fast can I read and write to these pins? Writing from, or sending signals, from the GPIO pins has , but the other way around has been more obscure. Here I answer the question and find some interesting, unexpected results!

The test

All the following tests were done as root in a Raspberry Pi Model B+ using a Jessie build of Raspbian (Raspberry Pi Model 2 is generally ). To calculate result rates, the commands were run using time (e.g. time program) and the real time result was used to divide into the total number of cycles or iterations to figure out the resulting rate.

How fast can you write to GPIO pins for outputing a signal?

I decided to test the two fastest languages - Python and Native C - to see how fast it could be done. Also, I included Go in the experiments, which is a language that has not been Tested date for generating square waves yet. Here are the results.

Language (linked to code) Tested date Result (cycle rate)
06/06/2015 69 kHz
06/06/2015 174 kHz
06/06/2015 15 MHz

My results for Python and C are similar to what was , but the Go result is new! The Go result is pretty unexpected - it seems to be the fastest language for writing to pins with the exception of C. I think this is thanks to a by .

How fast can you read from GPIO pins to memory?

Another question is how fast can you read? In this case I want to read a pin many times and store the value in virtual memory so there is no hard-disk storage here (which may be a bottleneck). I’m going to focus on the two fastest languages - Go and native C.

Language (linked to code) Tested date Result (read rate)
06/06/2015 1.6 Mhz
06/06/2015 7.2 MHz

Is reading harder or easier than writing for a given language? For C, reading actually seems to be harder, as it reads about half the rate it can write a cycle - so detecting pin changes is 4x slower than writing pin changes. However, Go can read faster than it can write! That’s pretty unexpected. Go seems like a good alternative to C for reading GPIO pins.

These read speeds are effectively the fastest you can possibly read. These programs read into memory and do nothing with the result. In a practical case you’d want to use the result - most likely by writing it to disk, thus you’ll have a bottleneck there immediately. This brings me to the final question:

How fast can you read from GPIO pins to disk?

This experiment is similar to the previous, except that here I use Go and C to compile the individual bits into bytes which are written to disk as a block every 1000 Bytes. The results are surprising:

Language (linked to code) Tested date Result (read + write-to-disk rate)
06/06/2015 440 kHz
06/06/2015 673 kHz

Here was the real surprise - Go creeps up on C in terms of speed! Go seems to be optimized for both reading the GPIO pin as well as continuous writing to disk. Given the ease of coding, it seems like the Go may be the best way to go for reading GPIO pins.

June 7, 2015

Motion Sensor Speech-to-text on a Raspberry Pi