IoT
Benchmark VPS KVM Inception Hosting
Ini sebagai lanjutan dari review Inception Hosting sebelumnya. Bedanya dulu saya mengulas berdasarkan OpenVZ, sekarang (akhirnya) yang KVM in-stock lagi. Dan ada promo diskon 50%, ya jelas saya angkut. 😉
Intinya saya sangat puas dengan kualitas VPS dari Inception Hosting, karena itu ga ragu untuk membeli VPS baru untuk menggantikan yang lama. Secara spesifikasi sih setara aslinya, tapi jelas saya lebih condong ke KVM apabila bisa dan terjangkau harganya. 😀
Spesifikasi VPS yang saya beli dan ulas kali ini:
- UK-SSD-KVM-1024
- 2 CPU Core (Equal Share)
- 1024 MB Ram
- 10 GB Pure NVMe SSD Disk space
- 1000 GB Bandwidth @ 1 gbit (shared)
- 1 x IPv4 address
- 1 x /64 IPv6
- Full daily backup
- €4.00/month
Diawali dengan informasi prosesornya:
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 2
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 94
Model name: Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz
Stepping: 3
CPU MHz: 3599.994
BogoMIPS: 7199.98
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
L3 cache: 16384K
NUMA node0 CPU(s): 0,1
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology eagerfpu pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch arat xsaveopt fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smapStruktur storage (NVMe):
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 8.9G 1.5G 7.0G 17% /
devtmpfs 492M 0 492M 0% /dev
tmpfs 497M 0 497M 0% /dev/shm
tmpfs 497M 19M 478M 4% /run
tmpfs 497M 0 497M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/0Kondisi memori saat masih baru terinstall sistem operasinya:
free -m
total used free shared buff/cache available
Mem: 993 91 290 18 612 715
Swap: 0 0 0
Dilanjutkan dengan benchmark umum sistemnya:
----------------------------------------------------------------------
CPU model : Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz
Number of cores : 2
CPU frequency : 3599.994 MHz
Total size of Disk : 8.9 GB (1.5 GB Used)
Total amount of Mem : 993 MB (91 MB Used)
Total amount of Swap : 0 MB (0 MB Used)
System uptime : 0 days, 0 hour 26 min
Load average : 0.00, 0.01, 0.05
OS : CentOS 7.4.1708
Arch : x86_64 (64 Bit)
Kernel : 3.10.0-123.4.2.el7.x86_64
----------------------------------------------------------------------
I/O speed(1st run) : 1.0 GB/s
I/O speed(2nd run) : 1.2 GB/s
I/O speed(3rd run) : 1.2 GB/s
Average I/O speed : 1160.5 MB/s
----------------------------------------------------------------------
Node Name IPv4 address Download Speed
CacheFly 205.234.175.175 111MB/s
Linode, Tokyo, JP 106.187.96.148 7.84MB/s
Linode, Singapore, SG 139.162.23.4 6.36MB/s
Linode, London, UK 176.58.107.39 108MB/s
Linode, Frankfurt, DE 139.162.130.8 51.3MB/s
Linode, Fremont, CA 50.116.14.9 6.61MB/s
Softlayer, Dallas, TX 173.192.68.18 11.1MB/s
Softlayer, Seattle, WA 67.228.112.250 9.86MB/s
Softlayer, Frankfurt, DE 159.122.69.4 63.6MB/s
Softlayer, Singapore, SG 119.81.28.170 6.99MB/s
Softlayer, HongKong, CN 119.81.130.170 5.81MB/s
----------------------------------------------------------------------
Node Name IPv6 address Download Speed
Linode, Atlanta, GA 2600:3c02::4b 15.0MB/s
Linode, Dallas, TX 2600:3c00::4b 5.46MB/s
Linode, Newark, NJ 2600:3c03::4b 16.0MB/s
Linode, Singapore, SG 2400:8901::4b 7.55MB/s
Linode, Tokyo, JP 2400:8900::4b 8.51MB/s
Softlayer, San Jose, CA 2607:f0d0:2601:2a::4 9.94MB/s
Softlayer, Washington, WA 2607:f0d0:3001:78::2 7.49MB/s
Softlayer, Paris, FR 2a03:8180:1301:8::4 83.4MB/s
Softlayer, Singapore, SG 2401:c900:1101:8::2 9.92MB/s
Softlayer, Tokyo, JP 2401:c900:1001:16::4 5.26MB/s
----------------------------------------------------------------------Ternyata I/O speednya lebih gila lagi, mencapai 1GB/s! Ini jauh lebih cepat dibandingkan milik saya sebelumnya yang juga NVMe. Mungkin karena node baru juga. Secara bandwidth masih 11-12, ya karena data center yang digunakan masih sama. Lokasinya juga masih di UK.
Seperti biasa, kita lanjutkan dengan tes performa sistem secara keseluruhan:
# # # # # # # ##### ###### # # #### # #
# # ## # # # # # # # ## # # # # #
# # # # # # ## ##### ##### # # # # ######
# # # # # # ## # # # # # # # # #
# # # ## # # # # # # # ## # # # #
#### # # # # # ##### ###### # # #### # #
Version 5.1.3 Based on the Byte Magazine Unix Benchmark
Multi-CPU version Version 5 revisions by Ian Smith,
Sunnyvale, CA, USA
January 13, 2011 johantheghost at yahoo period com
1 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10
1 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10
1 x Execl Throughput 1 2 3
1 x File Copy 1024 bufsize 2000 maxblocks 1 2 3
1 x File Copy 256 bufsize 500 maxblocks 1 2 3
1 x File Copy 4096 bufsize 8000 maxblocks 1 2 3
1 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10
1 x Pipe-based Context Switching 1 2 3 4 5 6 7 8 9 10
1 x Process Creation 1 2 3
1 x System Call Overhead 1 2 3 4 5 6 7 8 9 10
1 x Shell Scripts (1 concurrent) 1 2 3
1 x Shell Scripts (8 concurrent) 1 2 3
2 x Dhrystone 2 using register variables 1 2 3 4 5 6 7 8 9 10
2 x Double-Precision Whetstone 1 2 3 4 5 6 7 8 9 10
2 x Execl Throughput 1 2 3
2 x File Copy 1024 bufsize 2000 maxblocks 1 2 3
2 x File Copy 256 bufsize 500 maxblocks 1 2 3
2 x File Copy 4096 bufsize 8000 maxblocks 1 2 3
2 x Pipe Throughput 1 2 3 4 5 6 7 8 9 10
2 x Pipe-based Context Switching 1 2 3 4 5 6 7 8 9 10
2 x Process Creation 1 2 3
2 x System Call Overhead 1 2 3 4 5 6 7 8 9 10
2 x Shell Scripts (1 concurrent) 1 2 3
2 x Shell Scripts (8 concurrent) 1 2 3
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)
System: inception2.servernesia.com: GNU/Linux
OS: GNU/Linux -- 3.10.0-123.4.2.el7.x86_64 -- #1 SMP Mon Jun 30 16:09:14 UTC 2014
Machine: x86_64 (x86_64)
Language: en_US.utf8 (charmap="UTF-8", collate="UTF-8")
CPU 0: Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz (7200.0 bogomips)
x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET
CPU 1: Intel(R) Xeon(R) CPU E3-1270 v5 @ 3.60GHz (7200.0 bogomips)
x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET
19:30:57 up 47 min, 1 user, load average: 0.03, 0.04, 0.05; runlevel 3
------------------------------------------------------------------------
Benchmark Run: Wed Mar 21 2018 19:30:57 - 19:59:30
2 CPUs in system; running 1 parallel copy of tests
Dhrystone 2 using register variables 43432324.1 lps (10.0 s, 7 samples)
Double-Precision Whetstone 3954.4 MWIPS (12.9 s, 7 samples)
Execl Throughput 3643.2 lps (30.0 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 1098996.4 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 304239.3 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 2668632.3 KBps (30.0 s, 2 samples)
Pipe Throughput 1935019.4 lps (10.0 s, 7 samples)
Pipe-based Context Switching 382218.3 lps (10.0 s, 7 samples)
Process Creation 12835.3 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 8457.4 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 1600.3 lpm (60.0 s, 2 samples)
System Call Overhead 3161626.4 lps (10.0 s, 7 samples)
System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 43432324.1 3721.7
Double-Precision Whetstone 55.0 3954.4 719.0
Execl Throughput 43.0 3643.2 847.3
File Copy 1024 bufsize 2000 maxblocks 3960.0 1098996.4 2775.2
File Copy 256 bufsize 500 maxblocks 1655.0 304239.3 1838.3
File Copy 4096 bufsize 8000 maxblocks 5800.0 2668632.3 4601.1
Pipe Throughput 12440.0 1935019.4 1555.5
Pipe-based Context Switching 4000.0 382218.3 955.5
Process Creation 126.0 12835.3 1018.7
Shell Scripts (1 concurrent) 42.4 8457.4 1994.7
Shell Scripts (8 concurrent) 6.0 1600.3 2667.2
System Call Overhead 15000.0 3161626.4 2107.8
========
System Benchmarks Index Score 1763.3
------------------------------------------------------------------------
Benchmark Run: Wed Mar 21 2018 19:59:30 - 20:27:55
2 CPUs in system; running 2 parallel copies of tests
Dhrystone 2 using register variables 82255083.4 lps (10.0 s, 7 samples)
Double-Precision Whetstone 8606.6 MWIPS (11.3 s, 7 samples)
Execl Throughput 8528.0 lps (30.0 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 1453914.7 KBps (30.0 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 402764.4 KBps (30.0 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 4144739.4 KBps (30.0 s, 2 samples)
Pipe Throughput 3675534.0 lps (10.0 s, 7 samples)
Pipe-based Context Switching 710939.7 lps (10.0 s, 7 samples)
Process Creation 29246.3 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 12823.6 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 1837.1 lpm (60.0 s, 2 samples)
System Call Overhead 4751603.8 lps (10.0 s, 7 samples)
System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 82255083.4 7048.4
Double-Precision Whetstone 55.0 8606.6 1564.8
Execl Throughput 43.0 8528.0 1983.3
File Copy 1024 bufsize 2000 maxblocks 3960.0 1453914.7 3671.5
File Copy 256 bufsize 500 maxblocks 1655.0 402764.4 2433.6
File Copy 4096 bufsize 8000 maxblocks 5800.0 4144739.4 7146.1
Pipe Throughput 12440.0 3675534.0 2954.6
Pipe-based Context Switching 4000.0 710939.7 1777.3
Process Creation 126.0 29246.3 2321.1
Shell Scripts (1 concurrent) 42.4 12823.6 3024.4
Shell Scripts (8 concurrent) 6.0 1837.1 3061.9
System Call Overhead 15000.0 4751603.8 3167.7
========
System Benchmarks Index Score 2984.5Dan… secara keseluruhan performanya lebih baik sekitar 20%an dibandingkan OpenVZnya. Worth it lah.
Hasil tes GeekBench juga merefleksikan kesimpulan yang sama: lebih baik. Single core: 4577 dan Multicore: 7524. Linknya disini: https://browser.geekbench.com/v4/cpu/7579738
Mungkin OOT, tapi setelah saya amati soal OVZ dan KVM, saya lebih yakin bahwa OVZ lebih hemat resource (RAM+HDD) sedikit dibandingkan KVM untuk spesifikasi setara.
