-
-
Save pizthewiz/37997fffe9e2f2ba8d2e to your computer and use it in GitHub Desktop.
sysbench and mbw ODROID-C1
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
odroid@odroid-c1:~$ sysbench --test=cpu --num-threads=4 run | |
sysbench 0.4.12: multi-threaded system evaluation benchmark | |
Running the test with following options: | |
Number of threads: 4 | |
Doing CPU performance benchmark | |
Threads started! | |
Done. | |
Maximum prime number checked in CPU test: 10000 | |
Test execution summary: | |
total time: 54.7984s | |
total number of events: 10000 | |
total time taken by event execution: 219.1186 | |
per-request statistics: | |
min: 21.75ms | |
avg: 21.91ms | |
max: 41.81ms | |
approx. 95 percentile: 22.34ms | |
Threads fairness: | |
events (avg/stddev): 2500.0000/27.72 | |
execution time (avg/stddev): 54.7796/0.01 | |
odroid@odroid-c1:~$ sysbench --test=cpu --num-threads=1 run | |
sysbench 0.4.12: multi-threaded system evaluation benchmark | |
Running the test with following options: | |
Number of threads: 1 | |
Doing CPU performance benchmark | |
Threads started! | |
Done. | |
Maximum prime number checked in CPU test: 10000 | |
Test execution summary: | |
total time: 223.4491s | |
total number of events: 10000 | |
total time taken by event execution: 223.4396 | |
per-request statistics: | |
min: 22.33ms | |
avg: 22.34ms | |
max: 23.70ms | |
approx. 95 percentile: 22.35ms | |
Threads fairness: | |
events (avg/stddev): 10000.0000/0.00 | |
execution time (avg/stddev): 223.4396/0.00 | |
odroid@odroid-c1:~$ mbw 100 | |
Long uses 4 bytes. Allocating 2*26214400 elements = 209715200 bytes of memory. | |
Using 262144 bytes as blocks for memcpy block copy test. | |
Getting down to business... Doing 10 runs per test. | |
0 Method: MEMCPY Elapsed: 0.20271 MiB: 100.00000 Copy: 493.320 MiB/s | |
1 Method: MEMCPY Elapsed: 0.20267 MiB: 100.00000 Copy: 493.403 MiB/s | |
2 Method: MEMCPY Elapsed: 0.20258 MiB: 100.00000 Copy: 493.639 MiB/s | |
3 Method: MEMCPY Elapsed: 0.20257 MiB: 100.00000 Copy: 493.647 MiB/s | |
4 Method: MEMCPY Elapsed: 0.20254 MiB: 100.00000 Copy: 493.727 MiB/s | |
5 Method: MEMCPY Elapsed: 0.20293 MiB: 100.00000 Copy: 492.788 MiB/s | |
6 Method: MEMCPY Elapsed: 0.20256 MiB: 100.00000 Copy: 493.693 MiB/s | |
7 Method: MEMCPY Elapsed: 0.20259 MiB: 100.00000 Copy: 493.600 MiB/s | |
8 Method: MEMCPY Elapsed: 0.20247 MiB: 100.00000 Copy: 493.888 MiB/s | |
9 Method: MEMCPY Elapsed: 0.20245 MiB: 100.00000 Copy: 493.942 MiB/s | |
AVG Method: MEMCPY Elapsed: 0.20261 MiB: 100.00000 Copy: 493.565 MiB/s | |
0 Method: DUMB Elapsed: 0.10695 MiB: 100.00000 Copy: 935.043 MiB/s | |
1 Method: DUMB Elapsed: 0.10680 MiB: 100.00000 Copy: 936.295 MiB/s | |
2 Method: DUMB Elapsed: 0.10681 MiB: 100.00000 Copy: 936.277 MiB/s | |
3 Method: DUMB Elapsed: 0.10693 MiB: 100.00000 Copy: 935.191 MiB/s | |
4 Method: DUMB Elapsed: 0.10672 MiB: 100.00000 Copy: 937.005 MiB/s | |
5 Method: DUMB Elapsed: 0.10693 MiB: 100.00000 Copy: 935.235 MiB/s | |
6 Method: DUMB Elapsed: 0.10687 MiB: 100.00000 Copy: 935.690 MiB/s | |
7 Method: DUMB Elapsed: 0.10692 MiB: 100.00000 Copy: 935.252 MiB/s | |
8 Method: DUMB Elapsed: 0.10679 MiB: 100.00000 Copy: 936.382 MiB/s | |
9 Method: DUMB Elapsed: 0.10692 MiB: 100.00000 Copy: 935.279 MiB/s | |
AVG Method: DUMB Elapsed: 0.10686 MiB: 100.00000 Copy: 935.764 MiB/s | |
0 Method: MCBLOCK Elapsed: 0.09359 MiB: 100.00000 Copy: 1068.524 MiB/s | |
1 Method: MCBLOCK Elapsed: 0.09328 MiB: 100.00000 Copy: 1072.018 MiB/s | |
2 Method: MCBLOCK Elapsed: 0.09348 MiB: 100.00000 Copy: 1069.782 MiB/s | |
3 Method: MCBLOCK Elapsed: 0.09339 MiB: 100.00000 Copy: 1070.790 MiB/s | |
4 Method: MCBLOCK Elapsed: 0.09362 MiB: 100.00000 Copy: 1068.205 MiB/s | |
5 Method: MCBLOCK Elapsed: 0.09347 MiB: 100.00000 Copy: 1069.839 MiB/s | |
6 Method: MCBLOCK Elapsed: 0.09359 MiB: 100.00000 Copy: 1068.456 MiB/s | |
7 Method: MCBLOCK Elapsed: 0.09361 MiB: 100.00000 Copy: 1068.216 MiB/s | |
8 Method: MCBLOCK Elapsed: 0.09333 MiB: 100.00000 Copy: 1071.513 MiB/s | |
9 Method: MCBLOCK Elapsed: 0.09357 MiB: 100.00000 Copy: 1068.684 MiB/s | |
AVG Method: MCBLOCK Elapsed: 0.09349 MiB: 100.00000 Copy: 1069.601 MiB/s | |
odroid@odroid-c1:~$ uname -a | |
Linux odroid-c1 3.10.64-39 #1 SMP PREEMPT Thu Jan 22 02:46:33 BRST 2015 armv7l armv7l armv7l GNU/Linux |
Adafruit posted sysbench
results for both the B+ and 2 B, in their article Introducing the Raspberry Pi 2 - Model B. Their results for the B were a bit better than the run above:
Number of threads: 4
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 10000
Test execution summary:
total time: 76.1168s
total number of events: 10000
total time taken by event execution: 304.4156
per-request statistics:
min: 29.65ms
avg: 30.44ms
max: 63.32ms
approx. 95 percentile: 34.97ms
Threads fairness:
events (avg/stddev): 2500.0000/7.38
execution time (avg/stddev): 76.1039/0.01
single thread:
Running the test with following options:
Number of threads: 1
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 10000
Test execution summary:
total time: 298.6816s
total number of events: 10000
total time taken by event execution: 298.6632
per-request statistics:
min: 29.64ms
avg: 29.87ms
max: 44.60ms
approx. 95 percentile: 32.14ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 298.6632/0.00
And for the B+:
Running the test with following options:
Number of threads: 4
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 10000
Test execution summary:
total time: 523.1061s
total number of events: 10000
total time taken by event execution: 2091.9841
per-request statistics:
min: 162.66ms
avg: 209.20ms
max: 252.29ms
approx. 95 percentile: 232.33ms
Threads fairness:
events (avg/stddev): 2500.0000/1.22
execution time (avg/stddev): 522.9960/0.04
single thread:
Running the test with following options:
Number of threads: 1
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 10000
Test execution summary:
total time: 523.7819s
total number of events: 10000
total time taken by event execution: 523.7231
per-request statistics:
min: 51.99ms
avg: 52.37ms
max: 54.81ms
approx. 95 percentile: 53.54ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 523.7231/0.00
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For comparison Raspberry Pi 2 B (via http://pastebin.com/NqcKAtEQ):
and single thread (via http://pastebin.com/h07Lcpd8):