Difference between revisions of "Raspberry Pi - armv5tel vs armv6hl Benchmarks"
Chris Tyler (talk | contribs) (→sysbench cpu =) |
Chris Tyler (talk | contribs) (→sysbench cpu =) |
||
| Line 49: | Line 49: | ||
armv6hl is 34% faster than armv5tel | armv6hl is 34% faster than armv5tel | ||
| − | == sysbench cpu | + | == sysbench cpu == |
{|width="100%" cellborder="0" cellpadding="0" cellspacing="10" | {|width="100%" cellborder="0" cellpadding="0" cellspacing="10" | ||
|- | |- | ||
| − | |'''armv5tel'' | + | |'''armv5tel''' |
sysbench 0.4.12: multi-threaded system evaluation benchmark | sysbench 0.4.12: multi-threaded system evaluation benchmark | ||
| Line 82: | Line 82: | ||
events (avg/stddev): 10000.0000/0.00 | events (avg/stddev): 10000.0000/0.00 | ||
execution time (avg/stddev): 865.4254/0.00 | execution time (avg/stddev): 865.4254/0.00 | ||
| − | |'''armv6hl'' | + | |'''armv6hl''' |
| − | sysbench 0.4.12: multi-threaded system evaluation benchmark | + | sysbench 0.4.12: multi-threaded system evaluation benchmark |
| − | + | ||
| − | Running the test with following options: | + | Running the test with following options: |
| − | Number of threads: 1 | + | Number of threads: 1 |
| − | + | ||
| − | Doing CPU performance benchmark | + | Doing CPU performance benchmark |
| − | + | ||
| − | Threads started! | + | Threads started! |
| − | + | ||
| − | + | ||
| − | Done. | + | Done. |
| − | + | ||
| − | Maximum prime number checked in CPU test: 10000 | + | Maximum prime number checked in CPU test: 10000 |
| − | + | ||
| − | + | ||
| − | Test execution summary: | + | Test execution summary: |
| − | + | total time: 516.5632s | |
| − | + | total number of events: 10000 | |
| − | + | total time taken by event execution: 516.5205 | |
| − | + | per-request statistics: | |
| − | + | min: 51.06ms | |
| − | + | avg: 51.65ms | |
| − | + | max: 114.26ms | |
| − | + | approx. 95 percentile: 54.66ms | |
| − | + | ||
| − | Threads fairness: | + | Threads fairness: |
| − | + | events (avg/stddev): 10000.0000/0.00 | |
| − | + | execution time (avg/stddev): 516.5205/0.00 | |
| + | |} | ||
| − | + | armv5tel is 40% faster than armv6hl | |
Revision as of 15:01, 19 December 2012
Here are some preliminary armv5tel vs armv6hl benchmarks performed by Jordan Cwang 2012-12-12 to 2012-12-19:
GTKperf
armv5tel
GtkPerf 0.40 - Starting testing: Tue Dec 18 17:07:28 2012 GtkEntry - time: 0.92 GtkComboBox - time: 24.14 GtkComboBoxEntry - time: 15.32 GtkSpinButton - time: 3.96 GtkProgressBar - time: 3.67 GtkToggleButton - time: 4.65 GtkCheckButton - time: 3.02 GtkRadioButton - time: 4.23 GtkTextView - Add text - time: 10.61 GtkTextView - Scroll - time: 6.64 GtkDrawingArea - Lines - time: 27.90 GtkDrawingArea - Circles - time: 35.73 GtkDrawingArea - Text - time: 17.22 GtkDrawingArea - Pixbufs - time: 1.52 --- Total time: 159.62 |
armv6hl
GtkPerf 0.40 - Starting testing: Tue Dec 18 17:08:38 2012 GtkEntry - time: 0.74 GtkComboBox - time: 11.29 GtkComboBoxEntry - time: 6.57 GtkSpinButton - time: 1.11 GtkProgressBar - time: 0.72 GtkToggleButton - time: 1.44 GtkCheckButton - time: 1.23 GtkRadioButton - time: 2.10 GtkTextView - Add text - time: 9.34 GtkTextView - Scroll - time: 4.72 GtkDrawingArea - Lines - time: 21.16 GtkDrawingArea - Circles - time: 27.95 GtkDrawingArea - Text - time: 14.98 GtkDrawingArea - Pixbufs - time: 1.56 --- Total time: 104.97 |
armv6hl is 34% faster than armv5tel
sysbench cpu
armv5tel
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: 865.4808s
total number of events: 10000
total time taken by event execution: 865.4254
per-request statistics:
min: 84.33ms
avg: 86.54ms
max: 431.30ms
approx. 95 percentile: 90.00ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 865.4254/0.00
|
armv6hl
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: 516.5632s
total number of events: 10000
total time taken by event execution: 516.5205
per-request statistics:
min: 51.06ms
avg: 51.65ms
max: 114.26ms
approx. 95 percentile: 54.66ms
Threads fairness:
events (avg/stddev): 10000.0000/0.00
execution time (avg/stddev): 516.5205/0.00
|
armv5tel is 40% faster than armv6hl
