Google Cloud Platform sering saya temui disarankan bikin yang ingin VPS free dan dapat dikerjakan hosting WordPress. Memang tak ada yang salah, karena yang jenis f1-micro (1 vCPU, 0.6 GB memory, 10 GB) memang secara perhitungan billing GCP akan bebas biaya selamanya. Tetapi dikerjakan hosting situs? Kalau statis jelas mampu, tapi dinamis seperti WordPress ini yang saya sendiri belum tahu.
Apa yang kita dapatkan?
Secara prosesor ini datanya:
lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 85
Model name: Intel(R) Xeon(R) CPU @ 2.00GHz
Stepping: 3
CPU MHz: 2000.154
BogoMIPS: 4000.30
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 56320K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single pti fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsavesKemudian struktur storage:
df -hT
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 279M 0 279M 0% /dev
tmpfs tmpfs 59M 848K 58M 2% /run
/dev/sda1 ext4 9.6G 2.2G 7.4G 23% /
tmpfs tmpfs 291M 0 291M 0% /dev/shm
tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs tmpfs 291M 0 291M 0% /sys/fs/cgroup
/dev/loop0 squashfs 48M 48M 0 100% /snap/google-cloud-sdk/38
/dev/loop1 squashfs 87M 87M 0 100% /snap/core/4650
/dev/loop2 squashfs 87M 87M 0 100% /snap/core/4830
/dev/loop3 squashfs 49M 49M 0 100% /snap/google-cloud-sdk/40
/dev/loop4 squashfs 49M 49M 0 100% /snap/google-cloud-sdk/39
/dev/sda15 vfat 105M 3.4M 102M 4% /boot/efi
tmpfs tmpfs 59M 0 59M 0% /run/user/1001Dan kondisi memori default:
free -m
total used free shared buff/cache available
Mem: 581 161 73 0 347 318
Swap: 0 0 0Bagaimana kemampuannya?
Hasil Bench.sh
----------------------------------------------------------------------
CPU model : Intel(R) Xeon(R) CPU @ 2.00GHz
Number of cores : 1
CPU frequency : 2000.154 MHz
Total size of Disk : GB ( GB Used)
Total amount of Mem : 581 MB (165 MB Used)
Total amount of Swap : 0 MB (0 MB Used)
System uptime : 0 days, 0 hour 3 min
Load average : 0.36, 0.52, 0.24
OS : Ubuntu 18.04 LTS
Arch : x86_64 (64 Bit)
Kernel : 4.15.0-1009-gcp
----------------------------------------------------------------------
I/O speed(1st run) : 37.4 MB/s
I/O speed(2nd run) : 37.5 MB/s
I/O speed(3rd run) : 37.5 MB/s
Average I/O speed : 37.5 MB/s
----------------------------------------------------------------------
Node Name IPv4 address Unduh Speed
CacheFly 205.234.175.175 122MB/s
Linode, Tokyo, JP 106.187.96.148 9.21MB/s
Linode, Singapore, SG 139.162.23.4 6.12MB/s
Linode, London, UK 176.58.107.39 14.8MB/s
Linode, Frankfurt, DE 139.162.130.8 13.8MB/s
Linode, Fremont, CA 50.116.14.9 20.0MB/s
Softlayer, Dallas, TX 173.192.68.18 27.8MB/s
Softlayer, Seattle, WA 67.228.112.250 15.7MB/s
Softlayer, Frankfurt, DE 159.122.69.4 5.55MB/s
Softlayer, Singapore, SG 119.81.28.170 4.48MB/s
Softlayer, HongKong, CN 119.81.130.170 5.60MB/s
----------------------------------------------------------------------Ketika melihat kalau I/Onya dibatasi 37.5 MB/s ini malah mengenaskan, normalnya kalau HDD ya sekitar 90-100 MB/s. Tetapi soal bandwidth tak ada masalah, termasuk wajar.
Dilanjutkan dengan UnixBench:
# # # # # # # ##### ###### # # #### # #
# # ## # # # # # # # ## # # # # #
# # # # # # ## ##### ##### # # # # ######
# # # # # # ## # # # # # # # # #
# # # ## # # # # # # # ## # # # #
#### # # # # # ##### ###### # # #### # #
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
========================================================================
BYTE UNIX Benchmarks (Version 5.1.3)
System: servernesia: GNU/Linux
OS: GNU/Linux -- 4.15.0-1009-gcp -- #9-Ubuntu SMP Fri May 25 08:48:52 UTC 2018
Machine: x86_64 (x86_64)
Language: en_US.utf8 (charmap=UTF-8, collate=UTF-8)
CPU 0: Intel(R) Xeon(R) CPU @ 2.00GHz (4000.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSENTER/SYSEXIT, SYSCALL/SYSRET
08:21:43 up 9 min, 2 users, load average: 0.34, 0.59, 0.41; runlevel 5
------------------------------------------------------------------------
Benchmark Run: Mon Jun 25 2018 08:21:43 - 08:53:24
1 CPU in system; running 1 parallel copy of tests
Dhrystone 2 using register variables 12840503.3 lps (10.0 s, 7 samples)
Double-Precision Whetstone 894.4 MWIPS (32.5 s, 7 samples)
Execl Throughput 836.5 lps (30.0 s, 2 samples)
File Copy 1024 bufsize 2000 maxblocks 82736.4 KBps (30.1 s, 2 samples)
File Copy 256 bufsize 500 maxblocks 24554.5 KBps (30.2 s, 2 samples)
File Copy 4096 bufsize 8000 maxblocks 195879.9 KBps (30.0 s, 2 samples)
Pipe Throughput
261890.9 lps (10.1 s, 7 samples)
Pipe-based Context Switching 62587.2 lps (10.1 s, 7 samples)
Process Creation 2889.9 lps (30.2 s, 2 samples)
Shell Scripts (1 concurrent) 1212.5 lpm (60.1 s, 2 samples)
Shell Scripts (8 concurrent) 158.8 lpm (60.4 s, 2 samples)
System Call Overhead 177728.8 lps (10.1 s, 7 samples)
System Benchmarks Index Values BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 12840503.3 1100.3
Double-Precision Whetstone 55.0 894.4 162.6
Execl Throughput 43.0 836.5 194.5
File Copy 1024 bufsize 2000 maxblocks 3960.0 82736.4 208.9
File Copy 256 bufsize 500 maxblocks 1655.0 24554.5 148.4
File Copy 4096 bufsize 8000 maxblocks 5800.0 195879.9 337.7
Pipe Throughput 12440.0 261890.9 210.5
Pipe-based Context Switching 4000.0 62587.2 156.5
Process Creation 126.0 2889.9 229.4
Shell Scripts (1 concurrent) 42.4 1212.5 286.0
Shell Scripts (8 concurrent) 6.0 158.8 264.7
System Call Overhead 15000.0 177728.8 118.5
========
System Benchmarks Index Score 232.3Sebetulnya saya ga mengira akan serendah ini, ketika diakses lewat SSH dan operasionalnya lumayan responsif. Ini malah lebih rendah dari Scaleway. ? Tak ada benchmark GeekBench kali ini karena prosesnya selalu mati di tengah – tengah, jadi dapat adalah indikator bahwa sistemnya tak mampu.
Penutup
Akhirnya saya coba bagi hosting blog 2 mingguan (saya tinggal libur lebaran dan monitoring aktif) dengan trafik ala kadarnya, dan khusus f1-micro bikin saya kesimpulannya kalau tak terpaksa jangan.
Awalnya saya berniat review produk Google Cloud Platform yang terkecil ini, tapi semacam itu melihat hasil ahir dari benchmark dan memastikan dengan pemakaian standar (web server). Ya daripada data benchmarknya terbuang akan saya share disini. Lokasinya us-east1-b karena hanya lokasi ini yang ga bayar, kecuali kita mau gunakan saldo trialnya yang 300 USD berlaku setahun. ?
Ini bukan vonis bahwa GCP itu buruk, bukan. Tetapi khusus f1-micro yang adalah paket terkecil dan digratiskan oleh Google, pasti banyak yang ingin tahu (termasuk saya) bagaimana kemampuannya. Kalau gratisan saya ga komplain. ?
Yang pasti saya jadi ingin tahu bagi paket standardnya secara billing di jarak harga 5-10$ per bulan karena ini nanti dapat diperbandingkan seketika dengan produknya Vultr, DigitalOcean, Linode, dan UpCloud.
Sumber https://servernesia.com