Benchmark of Dell Vostro, Cubietruck and my new ASUS VivoPC

I’ve had my ASUS VivoPC for a few days now, which I have been busy setting up. It came with Win 8.1. I had a play with it, to see what all the fuss was about. I can’t say I was impressed with it. I bought the computer to run as a server. Win 8.1 had to go, as Windows is a poor choice as a server system.

I installed the latest version of Ubuntu server. In my opinion, it is a good compromise between stability, ease-of-use, software availability, and software freshness. I do like apt-get systems. I don’t really “get” Fedora. I’ve tried rolling releases in the past, and have come to the conclusion that they are a bad idea. They have too many stability issues, and they can gobble up a lot of bandwidth with their updates.

My basic plan is to install a system, apt-get any packages that I need, but no more. When a new release is made, I then upgrade the distribution. I am not especially concerned about software breakage. As long as I can log into the upgraded system, I can fix any configuration upgrades.

Slackware still rocks.

Here is what the VivoPC looks like:

vivo

Installing the new OS was a pain on account of secure boot, meaning I had to keep fiddling with the BIOS settings until the computer booted up the USB install system. After that, installation was straightforward.

Power consumption in Watts

Cubietruck 6W

ASUS VivoPC 11W

Dell Vostro-230 57W

The Cubietruck, unsurprisingly, merely sipped juice. The Vivo was nearly double that. I am very happy with that result, as the power supply was rated at 65W. So the power consumption was much less than I was expecting it to be. I was also pleasantly surprised by the Vostro. I was expecting power consumption to be far more than 57W.

CPU benchmark

I used sysbench on each computer, all running various flavours of Linux. The command I used was: sysbench –num-threads=4 –test=cpu –cpu-max-prime=100000 run

cubietruck results

Test execution summary:
    total time:                          3631.5301s
    total number of events:              10000
    total time taken by event execution: 14524.8766
    per-request statistics:
         min:                               1136.91ms
         avg:                               1452.49ms
         max:                               2098.23ms
         approx.  95 percentile:            1525.99ms

Threads fairness:
    events (avg/stddev):           2500.0000/3.61
    execution time (avg/stddev):   3631.2192/0.22

Vivo results

Test execution summary:
    total time:                          92.3525s
    total number of events:              10000
    total time taken by event execution: 369.3558
    per-request statistics:
         min:                                 36.26ms
         avg:                                 36.94ms
         max:                                 42.24ms
         approx.  95 percentile:              36.99ms

Threads fairness:
    events (avg/stddev):           2500.0000/3.08
    execution time (avg/stddev):   92.3389/0.01

Vostro results

Test execution summary:
    total time:                          120.2558s
    total number of events:              10000
    total time taken by event execution: 480.9613
    per-request statistics:
         min:                                 23.55ms
         avg:                                 48.10ms
         max:                                122.52ms
         approx.  95 percentile:              52.50ms

Threads fairness:
    events (avg/stddev):           2500.0000/9.25
    execution time (avg/stddev):   120.2403/0.01

Conclusion

Overall: Vivo > Vostro >> cubietruck

The Vivo is a much newer machine than the Vostro, so I would expect faster execution. The cubietruck was vastly slower than the others; not surprising considering the design of the device.

Fileio benchmark

I used the commands:

sysbench –test=fileio –file-total-size=6G prepare
sysbench –test=fileio –file-total-size=6G –file-test-mode=rndrw –max-time=300 –max-requests=0 –file-extra-flags=direct run
sysbench –test=fileio –file-total-size=6G cleanup

(link

The results are below.

Cubietruck results

Running the test with following options:
Number of threads: 1

Extra file open flags: 65536
128 files, 48Mb each
6Gb total file size
Block size 16Kb
Number of random requests for random IO: 0
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing random r/w test
Threads started!
Time limit exceeded, exiting…
Done.

Operations performed:  12240 Read, 8160 Write, 25985 Other = 46385 Total
Read 191.25Mb  Written 127.5Mb  Total transferred 318.75Mb  (1.0624Mb/sec)
   67.99 Requests/sec executed

Test execution summary:
    total time:                          300.0361s
    total number of events:              20400
    total time taken by event execution: 268.7123
    per-request statistics:
         min:                                  0.30ms
         avg:                                 13.17ms
         max:                                 95.97ms
         approx.  95 percentile:              35.16ms

Threads fairness:
    events (avg/stddev):           20400.0000/0.00
    execution time (avg/stddev):   268.7123/0.00

Vivo results

Running the test with following options:
Number of threads: 1

Extra file open flags: 16384
128 files, 48Mb each
6Gb total file size
Block size 16Kb
Number of random requests for random IO: 0
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing random r/w test
Threads started!
Time limit exceeded, exiting…
Done.

Operations performed:  20802 Read, 13868 Write, 44288 Other = 78958 Total
Read 325.03Mb  Written 216.69Mb  Total transferred 541.72Mb  (1.8057Mb/sec)
  115.57 Requests/sec executed

Test execution summary:
    total time:                          300.0043s
    total number of events:              34670
    total time taken by event execution: 197.3885
    per-request statistics:
         min:                                  0.23ms
         avg:                                  5.69ms
         max:                                149.36ms
         approx.  95 percentile:              13.86ms

Threads fairness:
    events (avg/stddev):           34670.0000/0.00
    execution time (avg/stddev):   197.3885/0.00

Vostro results

Running the test with following options:
Number of threads: 1

Extra file open flags: 16384
128 files, 48Mb each
6Gb total file size
Block size 16Kb
Number of random requests for random IO: 0
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing random r/w test
Threads started!
Time limit exceeded, exiting…
Done.

Operations performed:  21608 Read, 14405 Write, 46080 Other = 82093 Total
Read 337.62Mb  Written 225.08Mb  Total transferred 562.7Mb  (1.8757Mb/sec)
  120.04 Requests/sec executed

Test execution summary:
    total time:                          300.0032s
    total number of events:              36013
    total time taken by event execution: 193.5836
    per-request statistics:
         min:                                  0.20ms
         avg:                                  5.38ms
         max:                                240.23ms
         approx.  95 percentile:              12.42ms

Threads fairness:
    events (avg/stddev):           36013.0000/0.00
    execution time (avg/stddev):   193.5836/0.00

Conclusion

Vostro > Vivo > Cubietruck

Other notes

My VivoPC is very quiet compared to the Vostro, but noisier than the cubietruck.

Advertisements

About mcturra2000

Computer programmer living in Scotland.
This entry was posted in Computers. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s