Vultr VPS Review (Tokyo)

Today, I developed an urge to try out the Vultr VPS service. I put in $5 and got a credit of $5. With the $10 in my control, I grabbed a VPS with the following specifications:

1 CPU
1024MB MEMORY
20GB STORAGE
200 GB TRANSFER
Monthly$7.00
Hourly$0.01

All the disks are supposed to be 100% SSD Storage. The CPUs are supposed to be 3+GHz CPUs.

I chose the Tokyo (Asia) location.

Let’s see how the VPS performs:

To check the load on the VPS and whether it is oversold:


root@xyz:~# top

top - 18:01:12 up 2:25, 1 user, load average: 0.00, 0.01, 0.05
Tasks: 80 total, 1 running, 78 sleeping, 1 stopped, 0 zombie
%Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 1017788 total, 757844 used, 259944 free, 40472 buffers
KiB Swap: 0 total, 0 used, 0 free. 475348 cached Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1278 root 20 0 105780 4112 3068 S 0.3 0.4 0:00.44 sshd
1 root 20 0 33380 2268 1000 S 0.0 0.2 0:00.72 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
6 root 20 0 0 0 0 S 0.0 0.0 0:01.30 kworker/u2:0
7 root 20 0 0 0 0 S 0.0 0.0 0:00.27 rcu_sched
8 root 20 0 0 0 0 S 0.0 0.0 0:00.32 rcuos/0
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcuob/0
11 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
12 root rt 0 0 0 0 S 0.0 0.0 0:00.03 watchdog/0
13 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper
14 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kdevtmpfs
15 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns
16 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 writeback
17 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kintegrityd
root@xyz #

To check the RAM usage:


root@xyz # free -m
total used free shared buffers cached
Mem: 993 724 269 65 39 464
-/+ buffers/cache: 220 773
Swap: 0 0 0
root@xyz #

Lets see the CPU processor:


root@xyz # cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Vultr Virtual CPU 2
stepping : 1
microcode : 0x1
cpu MHz : 3392.156
cache size : 4096 KB
cpu cores : 1
root@xyz #

Lets see how fast the disk is (I/O):


root@xyz# dd if=/dev/zero of=test bs=64k count=16k conv=fdatasync
16384+0 records in
16384+0 records out
1073741824 bytes (1.1 GB) copied, 2.34592 s, 458 MB/s
root@xyz #

Checking the download speed of the VPS using wget:


root@xyz # wget cachefly.cachefly.net/100mb.test
--2014-08-21 18:04:05-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: '100mb.test'

100%[======================================>] 104,857,600 96.0MB/s in 1.0s

2014-08-21 18:04:06 (96.0 MB/s) - '100mb.test' saved [104857600/104857600]

root@xyz #

Checking the Upload & Download Speeds using the python tool:


root@xyz:~# python speedtest-cli
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Choopa, LLC (108.61.223.225)...
Selecting best server based on latency...
Hosted by World's Fastest Indian (Tokyo) [1.39 km]: 104.652 ms
Testing download speed........................................
Download: 61.03 Mbits/s
Testing upload speed..................................................
Upload: 83.14 Mbits/s
root@xyz #

All-in-one-test using the automated script:


root@xyz:~# bash bench.sh
CPU model : Vultr Virtual CPU 2
Number of cores : 1
CPU frequency : 3392.156 MHz
Total amount of ram : 993 MB
Total amount of swap : 0 MB
System uptime : 2:31,
Download speed : (98.8MB/s)
I/O speed : 461MB/s
root@xyz:~#

The price is obviously rock-bottom. I don’t think you will ever get a pure SSD disk with such a configuration at such a low price.

Now, what I have to check the stability of the network at different times of the day. I also have to check what the support service is like.

Watch this space.

Leave a Reply

Your email address will not be published. Required fields are marked *