Beberapa waktu yang lalu HardCloud.net – salah satu provider VPS yang bermarkas di USA melakukan ujicoba layanan VM berbasis nebulacloud. Ujicoba ini diadakan di komunitas LowEndTalk dan berlangsung kurang lebih selama 2 minggu – dari pertengahan Desember 2013 dan berakhir di awal Januari 2014. Berikut adalah hasil benchmark singkat yang saya lakukan di cloud mereka.
Spesifikasi VM :
- CPU single core 2.5 GHz
- RAM 1 Gb
- Swap 384 Mb
- KVM-based
- Diskspace 10 Gb
- OS Debian 7 x64
- Datacenter / ISP Affinity Internet, US
FreeVPS benchmark script
# wget freevps.us/downloads/bench.sh -O - -o /dev/nul | bash CPU model : QEMU Virtual CPU version (cpu64-rhel6) Number of cores : 1 CPU frequency : 2499.998 MHz Total amount of ram : 1002 MB Total amount of swap : 382 MB System uptime : 17 min, Download speed from CacheFly: 5.11MB/s Download speed from Coloat, Atlanta GA: 4.63MB/s Download speed from Softlayer, Dallas, TX: 1.35MB/s Download speed from Linode, Tokyo, JP: 910KB/s Download speed from i3d.net, Rotterdam, NL: 804KB/s Download speed from Leaseweb, Haarlem, NL: 562KB/s Download speed from Softlayer, Singapore: 598KB/s Download speed from Softlayer, Seattle, WA: 909KB/s Download speed from Softlayer, San Jose, CA: 871KB/s Download speed from Softlayer, Washington, DC: 1.10MB/s I/O speed : 24.4 MB/s
Koneksi ke Asia, Eropa, dan sebagian US rada ancur – hal ini mungkin karena routing yang tidak di optimize, koneksi yang tidak prima, atau memang karena sedang di “stress” habis-habisan oleh betatester. I/O speed VM juga buruk :(
Speedtest.net
# ./speedtest-cli --simple --share Ping: 63.101 ms Download: 56.43 Mbit/s Upload: 45.21 Mbit/s Share results: http://www.speedtest.net/result/3198420932.png
Speedtest menunjukkan hasil yang tidak terlalu buruk.
Test download, ping dan traceroute
# wget http://cachefly.cachefly.net/10mb.test --2013-12-31 15:41:12-- http://cachefly.cachefly.net/10mb.test Resolving cachefly.cachefly.net... 205.234.175.175 Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10485760 (10M) [application/octet-stream] Saving to: `10mb.test' 100%[======================================>] 10,485,760 4.68M/s in 2.1s 2013-12-31 15:41:14 (4.68 MB/s) - `10mb.test' saved [10485760/10485760] # traceroute cachefly.cachefly.net traceroute to cachefly.cachefly.net (205.234.175.175), 30 hops max, 60 byte packets 1 207.234.136.1 (207.234.136.1) 1.427 ms 1.262 ms 1.159 ms 2 te3-4.co2.as30217.net (84.40.24.50) 1.015 ms 0.847 ms 0.653 ms 3 te3-4.co1.as30217.net (84.40.24.49) 1.602 ms 1.097 ms 0.919 ms 4 te-1-4.car3.Tampa1.Level3.net (4.71.0.29) 0.736 ms 0.639 ms 0.591 ms 5 ae-13-13.car1.Tampa1.Level3.net (4.69.133.17) 237.276 ms 237.514 ms 258.557 ms 6 ae-2-5.bar1.Tampa1.Level3.net (4.69.133.14) 35.301 ms 2.545 ms 2.048 ms 7 ae-5-5.ebr1.Miami1.Level3.net (4.69.148.213) 7.926 ms 7.797 ms 7.650 ms 8 ae-1-51.edge1.Miami2.Level3.net (4.69.138.75) 38.713 ms 6.147 ms 6.044 ms 9 4.68.127.54 (4.68.127.54) 6.671 ms 6.555 ms 6.552 ms 10 xe-0-2-0.cr1.mia1.us.nlayer.net (63.141.207.4) 6.220 ms 7.181 ms xe-1-0-0.cr1.mia1.us.nlayer.net (63.141.207.6) 6.952 ms 11 vip1.G-anycast1.cachefly.net (205.234.175.175) 6.816 ms 6.650 ms 32.848 ms # ping cachefly.cachefly.net -c 10 PING vip1.g.cachefly.net (205.234.175.175) 56(84) bytes of data. 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=1 ttl=57 time=6.54 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=2 ttl=57 time=6.42 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=3 ttl=57 time=6.29 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=4 ttl=57 time=19.4 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=5 ttl=57 time=6.16 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=6 ttl=57 time=6.27 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=7 ttl=57 time=6.41 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=8 ttl=57 time=6.32 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=9 ttl=57 time=6.21 ms 64 bytes from vip1.G-anycast1.cachefly.net (205.234.175.175): icmp_req=10 ttl=57 time=6.38 ms --- vip1.g.cachefly.net ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9024ms rtt min/avg/max/mdev = 6.163/7.652/19.493/3.948 ms
ioping
# ioping / -c 10 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=1 time=708 us 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=2 time=1.0 ms 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=3 time=1.4 ms 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=4 time=882 us 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=5 time=1.6 ms 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=6 time=1.1 ms 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=7 time=1.9 ms 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=8 time=998 us 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=9 time=1.6 ms 4.0 KiB from / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f): request=10 time=1.1 ms --- / (ext3 /dev/disk/by-uuid/5309b3f9-2b10-40a4-aa03-0ff45a6dab7f) ioping statistics --- 10 requests completed in 9.0 s, 816 iops, 3.2 MiB/s min/avg/max/mdev = 708 us / 1.2 ms / 1.9 ms / 352 us
ioping menunjukkan hasil yang tidak konsisten. (banyak yang melakukan stress test, maybe)
dd test
# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync ; rm -f test 16384+0 records in 16384+0 records out 1073741824 bytes (1.1 GB) copied, 12.3566 s, 86.9 MB/s # dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync ; rm -f test 16384+0 records in 16384+0 records out 1073741824 bytes (1.1 GB) copied, 6.78196 s, 158 MB/s
Terlihat hasil dd juga fluktuatif.
Kesimpulan
Hasil test ini diambil saat kondisi nodes dalam keadaan yang tidak stabil, jadi nggak bisa diambil patokan apakah NebulaCloud milik HardCloud memiliki kualitas yang baik atau tidak. Yang jelas, saat testbed ditutup pihak HardCloud sudah banyak melakukan perbaikan disisi teknis dan kinerja server. Well, kita tunggu saja launching layanan NebulaCloud VM dari HardCloud. :)
