I picked up a bricked E02 on eBay and was able to fix it with serial console. I thought it the appropriate time to compare the performance with my Pro. Here are some benchmarks for both devices using a Sandisk 16GB Ultra Fit 3.0 Flash Drive on both and then a 320gb 7200rpm Seagate 2.5 drive in Esata enclosure for the Pro:
Pogoplug E02 USB with latest u-boot and 3.17.0 rootfs:
Pogoplug Pro @850Mhz USB with latest u-boot and 3.18.5 rootfs:
Pogoplug Pro @ 850Mhz SATA with latest u-boot and 3.18.5 rootfs:
I am not sure why the E02 is not doing as well as the Pro. I thought even overclocked the Pro would barely manage to reach an E02's sysbench . Wrong assumption? Maybe I am doing something wrong? Comments appreciated.
Also, if you wanna compare sysbench numbers to some more modern SOC's, look here: http://wiki.glidernet.org/cpu-boards
Pogoplug E02 USB with latest u-boot and 3.17.0 rootfs:
root@pogoplug:~# uname -a
Linux 3.17.0-kirkwood-tld-1 #4 PREEMPT Wed Oct 22 00:55:17 PDT 2014 armv5tel GNU/Linux
root@pogoplug:~# hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 528 MB in 2.00 seconds = 263.77 MB/sec
Timing buffered disk reads: 86 MB in 3.07 seconds = 28.02 MB/sec
root@pogoplug:~# sysbench --test=cpu --cpu-max-prime=2000 --num-threads=2 run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 2
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 2000
Test execution summary:
total time: 102.3354s
total number of events: 10000
total time taken by event execution: 204.6112
per-request statistics:
min: 10.22ms
avg: 20.46ms
max: 40.25ms
approx. 95 percentile: 20.30ms
Threads fairness:
events (avg/stddev): 5000.0000/0.00
execution time (avg/stddev): 102.3056/0.02
Pogoplug Pro @850Mhz USB with latest u-boot and 3.18.5 rootfs:
root@debian:~# uname –a
Linux debian 3.18.5-oxnas-tld-1 #2 SMP PREEMPT Thu Feb 12 11:17:40 PST 2015 armv6l GNU/Linux
root@debian:~# hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 506 MB in 2.00 seconds = 252.62 MB/sec
Timing buffered disk reads: 84 MB in 3.06 seconds = 27.46 MB/sec
root@debian:~# sysbench --test=cpu --cpu-max-prime=2000 --num-threads=2 run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 2
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 2000
Test execution summary:
total time: 59.7179s
total number of events: 10000
total time taken by event execution: 119.4018
per-request statistics:
min: 11.70ms
avg: 11.94ms
max: 44.25ms
approx. 95 percentile: 12.46ms
Threads fairness:
events (avg/stddev): 5000.0000/29.00
execution time (avg/stddev): 59.7009/0.00
.
Pogoplug Pro @ 850Mhz SATA with latest u-boot and 3.18.5 rootfs:
root@debian:~# uname -a
Linux debian 3.18.5-oxnas-tld-1 #2 SMP PREEMPT Thu Feb 12 11:17:40 PST 2015 armv6l GNU/Linux
root@debian:~# hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 512 MB in 2.01 seconds = 255.36 MB/sec
Timing buffered disk reads: 266 MB in 3.00 seconds = 88.54 MB/sec
root@debian:~# sysbench --test=cpu --cpu-max-prime=2000 --num-threads=2 run
sysbench 0.4.12: multi-threaded system evaluation benchmark
Running the test with following options:
Number of threads: 2
Doing CPU performance benchmark
Threads started!
Done.
Maximum prime number checked in CPU test: 2000
Test execution summary:
total time: 59.7617s
total number of events: 10000
total time taken by event execution: 119.4815
per-request statistics:
min: 11.70ms
avg: 11.95ms
max: 57.55ms
approx. 95 percentile: 12.46ms
Threads fairness:
events (avg/stddev): 5000.0000/32.00
execution time (avg/stddev): 59.7407/0.01
I am not sure why the E02 is not doing as well as the Pro. I thought even overclocked the Pro would barely manage to reach an E02's sysbench . Wrong assumption? Maybe I am doing something wrong? Comments appreciated.
Also, if you wanna compare sysbench numbers to some more modern SOC's, look here: http://wiki.glidernet.org/cpu-boards