sudo yum install wget glibc.i686 libstdc++ libstdc++.i686<\/pre>\n\n\n\n
With the prerequisites fulfilled, go ahead and download the benchmark package. On a good network, the download is almost instantaneous, but should not take long in any case.<\/p>\n\n\n\n
wget http:\/\/cdn.primatelabs.com\/Geekbench-3.4.1-Linux.tar.gz ~\/<\/pre>\n\n\n\n
Afterwards, unpack the files and switch to the newly created folder. The following command will do just that.<\/p>\n\n\n\n
tar -zxvf ~\/Geekbench-3.4.1-Linux.tar.gz && cd ~\/dist\/Geekbench-3.4.1-Linux\/<\/pre>\n\n\n\n
Finally, you can run the benchmark with the command below.<\/p>\n\n\n\n
.\/geekbench<\/pre>\n\n\n\n
The Geekbench 3 performs a series of tests to measure the CPU performance with integer and floating point tasks as well as collects memory bandwidth data to rate the system memory. Once complete, you will see an output\u00a0similar to the example underneath.<\/p>\n\n\n\n
Open the first link in your web browser to view the results. Alternatively, if you register on the Geekbench website, you can use the second link to claim the results to your profile. Claiming the results allows you to save and compare the scores later.<\/p>\n\n\n\n
Upload succeeded. Visit the following link and view your results online:\n\n http:\/\/browser.primatelabs.com\/geekbench3\/6088030\n\nVisit the following link and add this result to your profile:\n\n http:\/\/browser.primatelabs.com\/geekbench3\/claim\/6088030?key=<\/pre>\n\n\n\n
The total score is scaled directly one-to-one to the CPU performance; double the score means double the performance. The scoring system is calibrated against a baseline score of 2500, which is the result for an Intel Core i5-2520M @ 2.50 GHz.<\/p>\n\n\n\n
fio<\/h2>\n\n\n\n
A big part of the overall performance of a cloud server comes from the storage device’s read and write speeds. A\u00a0good option to use for this purpose is fio<\/em>, which is an I\/O benchmarking and stress testing tool available on a multitude of platforms.\u00a0Install fio using the commands applicable to your system below.<\/p>\n\n\n\n
Debian and Ubuntu<\/h3>\n\n\n\n
sudo apt-get install fio<\/pre>\n\n\n\n
CentOS<\/h3>\n\n\n\n
sudo yum install wget libaio libibverbs librdmacm librbd1-devel\nwget https:\/\/kojipkgs.fedoraproject.org\/packages\/fio\/2.2.8\/2.el7\/x86_64\/fio-2.2.8-2.el7.x86_64.rpm ~\/\nsudo rpm -iv ~\/fio-2.2.8-2.el7.x86_64.rpm<\/pre>\n\n\n\n
IOPS is a measuring unit of input\/output operations per second and is a commonly\u00a0used performance metric for storage devices. The usual way to test IOPS is to perform random read and write operations, with fio this can be done using the three examples below.<\/p>\n\n\n\n
Random read\/write performance<\/h5>\n\n\n\n
fio --name=randrw --ioengine=libaio --direct=1 --bs=4k --iodepth=64 --size=4G --rw=randrw --rwmixread=75 --gtod_reduce=1<\/pre>\n\n\n\n
Random read performance<\/h5>\n\n\n\n
fio --name=randread --ioengine=libaio --direct=1 --bs=4k --iodepth=64 --size=4G --rw=randread --gtod_reduce=1<\/pre>\n\n\n\n
Random write performance<\/h5>\n\n\n\n
fio --name=randwrite --ioengine=libaio --direct=1 --bs=4k --iodepth=64 --size=4G --rw=randwrite --gtod_reduce=1<\/pre>\n\n\n\n
As with the Geekbench scores, the higher the IOPS, the faster the storage. For comparison, a standard\u00a07,200 rpm SATA drive HDD would have a score of 75-100 IOPS.<\/p>\n\n\n\n
IOPing<\/h2>\n\n\n\n
Another way to benchmark storage performance is to measure the latency\u00a0on individual requests. IOPing is a simple tool that does just that. It runs I\/O requests to the storage device to\u00a0benchmark the time to reply. The results display\u00a0disk latency in the same way the ping <\/em>test measures network latency.<\/p>\n\n\n\n
Debian and Ubuntu<\/h5>\n\n\n\n
wget https:\/\/launchpad.net\/ubuntu\/+archive\/primary\/+files\/ioping_0.9-2_amd64.deb ~\/\nsudo dpkg -i ~\/ioping_0.9-2_amd64.deb<\/pre>\n\n\n\n
CentOS<\/h5>\n\n\n\n
wget https:\/\/kojipkgs.fedoraproject.org\/packages\/ioping\/0.9\/1.el7\/x86_64\/ioping-0.9-1.el7.x86_64.rpm ~\/\nsudo rpm -iv ~\/ioping-0.9-1.el7.x86_64.rpm<\/pre>\n\n\n\n
Then run the test with the command below.<\/p>\n\n\n\n
ioping -c 10 .<\/pre>\n\n\n\n
The output will show something similar to the example underneath. The time shows the I\/O latency measured in microseconds.<\/p>\n\n\n\n
4 KiB from . (ext4 \/dev\/vda1): request=1 time=78 us\n4 KiB from . (ext4 \/dev\/vda1): request=2 time=175 us\n4 KiB from . (ext4 \/dev\/vda1): request=3 time=167 us\n4 KiB from . (ext4 \/dev\/vda1): request=4 time=174 us\n4 KiB from . (ext4 \/dev\/vda1): request=5 time=168 us\n4 KiB from . (ext4 \/dev\/vda1): request=6 time=185 us\n4 KiB from . (ext4 \/dev\/vda1): request=7 time=179 us\n4 KiB from . (ext4 \/dev\/vda1): request=8 time=178 us\n4 KiB from . (ext4 \/dev\/vda1): request=9 time=177 us\n4 KiB from . (ext4 \/dev\/vda1): request=10 time=195 us\n--- . (ext4 \/dev\/vda1) ioping statistics ---\n10 requests completed in 9.00 s, 5.97 k iops, 23.3 MiB\/s\nmin\/avg\/max\/mdev = 78 us \/ 167 us \/ 195 us \/ 30 us<\/pre>\n\n\n\n
The latency number measures the delay in response, which means the lower the delay, the better the performance.<\/p>\n\n\n\n
Conclusions<\/h2>\n\n\n\n
Cloud server benchmarking tools are a very convenient way to compare performance between cloud service providers. They are readily available and straightforward to use regardless of the operating systems available. Performance-demanding web applications might see a noticeable\u00a0difference in the quality of the service when running on genuinely capable hardware, but\u00a0even if you are not worried about numbers you should still know what you are getting for your money.<\/p>\n\n\n\n
If you wish to read more about benchmarking between cloud server providers, check out our Cloud Benchmark at Slush<\/a> blog post for how DigitalOcean and AWS EC2 fared against UpCloud. Also, if you are still unsure about cloud server performance, go ahead and find out more about our Cloud Server vs. VPS vs. Dedicated Server<\/a> comparison.<\/p>\n","protected":false},"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","community-category":[113],"class_list":["post-24594","tutorial","type-tutorial","status-publish","hentry","community-category-integrations"],"acf":[],"_links":{"self":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial\/24594","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/types\/tutorial"}],"replies":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/comments?post=24594"}],"wp:attachment":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media?parent=24594"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/community-category?post=24594"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}