About VPS in Malaysia
I'm searching for good and cheap VPS in Malaysia for few years. From my result, it's really difficult to find an affordable VPS hosting in Asia region especially in Malaysia. Besides Nocser, I really can't see any providers able to provide a VPS hosting with low price and good services.
Fortunately, I recently found a new VPS provider in Malaysia with very SEO friendly name as VPSMalaysia. The domain is registered in Febrary 2012, which is pretty new. However, their 256MB OpenVZ package priced at MYR25.90/month (~USD $8.50) tempted me.
Since they are new, I got a 7 days trial from them. A quick summary of the trial VPS is as below:
CPU Model : Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
CPU Cores : 8
CPU Frequency : 1250.094 MHz
Total Memory : 1024 MB
Total Swap : 1024 MB
Download Speed : 118KB/s
Disk I/O Speed : 62.0 MB/s
Their server is located at AIMS data center which is one of the cheapest data center in Malaysia. As usual, VPSMalaysia is using SolusVM for the VPS control panel which is standard in this industry. The performance is very good. I can compile codes and process large data in short time. I can't find any oversell symptoms at this moment, but I hope they can keep the performance in future too as their clients increasing.
If anyone need a bencmark result, here is it. The score is good 
I hope my review helps someone.
========================================================================
BYTE UNIX Benchmarks (Version 5.1.2)
System: s05.seikan.me: GNU/Linux
OS: GNU/Linux -- 2.6.32-042stab049.6 -- #1 SMP Mon Feb 6 19:17:43 MSK 2012
Machine: i686 (unknown)
Language: en_US.utf8 (charmap="ANSI_X3.4-1968", collate="ANSI_X3.4-1968")
CPU 0: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (5000.4 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
CPU 1: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (4999.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
CPU 2: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (4999.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
CPU 3: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (4999.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
CPU 4: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (4999.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
CPU 5: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (4999.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
CPU 6: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (4999.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
CPU 7: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (4999.3 bogomips)
Hyper-Threading, x86-64, MMX, Physical Address Ext, SYSCALL/SYSRET, Intel virtualization
11:36:28 up 1 day, 30 min, 1 user, load average: 0.10, 0.08, 0.03; runlevel 2
------------------------------------------------------------------------
Benchmark Run: Fri Apr 06 2012 11:36:28 - 12:04:54
8 CPUs in system; running 1 parallel copy of tests
Dhrystone 2 using register variables 12665268.2 lps (10.0 s, 7 samples)
Double-Precision Whetstone 2430.7 MWIPS (10.1 s, 7 samples)
Execl Throughput 2711.5 lps (29.3 s, 2 samples)
Pipe Throughput 796772.8 lps (10.0 s, 7 samples)
Pipe-based Context Switching 107737.8 lps (10.0 s, 7 samples)
Process Creation 4970.8 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 4797.4 lpm (60.0 s, 2 samples)
Shell Scripts (16 concurrent) 963.7 lpm (60.0 s, 2 samples)
Shell Scripts (8 concurrent) 1925.1 lpm (60.0 s, 2 samples)
System Call Overhead 622750.2 lps (10.0 s, 7 samples)
System Benchmarks Partial Index BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 12665268.2 1085.3
Double-Precision Whetstone 55.0 2430.7 442.0
Execl Throughput 43.0 2711.5 630.6
Pipe Throughput 12440.0 796772.8 640.5
Pipe-based Context Switching 4000.0 107737.8 269.3
Process Creation 126.0 4970.8 394.5
Shell Scripts (1 concurrent) 42.4 4797.4 1131.5
Shell Scripts (16 concurrent) --- 963.7 ---
Shell Scripts (8 concurrent) 6.0 1925.1 3208.5
System Call Overhead 15000.0 622750.2 415.2
========
System Benchmarks Index Score (Partial Only) 679.8
------------------------------------------------------------------------
Benchmark Run: Fri Apr 06 2012 12:04:54 - 12:36:49
8 CPUs in system; running 8 parallel copies of tests
Dhrystone 2 using register variables 49951660.4 lps (10.0 s, 7 samples)
Double-Precision Whetstone 18003.4 MWIPS (10.1 s, 7 samples)
Execl Throughput 10387.2 lps (29.1 s, 2 samples)
Pipe Throughput 3170190.2 lps (10.0 s, 7 samples)
Pipe-based Context Switching 612587.1 lps (10.0 s, 7 samples)
Process Creation 23317.1 lps (30.0 s, 2 samples)
Shell Scripts (1 concurrent) 14052.6 lpm (60.0 s, 2 samples)
Shell Scripts (16 concurrent) 941.2 lpm (60.2 s, 2 samples)
Shell Scripts (8 concurrent) 1891.1 lpm (60.1 s, 2 samples)
System Call Overhead 1276846.1 lps (10.0 s, 7 samples)
System Benchmarks Partial Index BASELINE RESULT INDEX
Dhrystone 2 using register variables 116700.0 49951660.4 4280.3
Double-Precision Whetstone 55.0 18003.4 3273.4
Execl Throughput 43.0 10387.2 2415.6
Pipe Throughput 12440.0 3170190.2 2548.4
Pipe-based Context Switching 4000.0 612587.1 1531.5
Process Creation 126.0 23317.1 1850.6
Shell Scripts (1 concurrent) 42.4 14052.6 3314.3
Shell Scripts (16 concurrent) --- 941.2 ---
Shell Scripts (8 concurrent) 6.0 1891.1 3151.9
System Call Overhead 15000.0 1276846.1 851.2
========
System Benchmarks Index Score (Partial Only) 2348.5
[Source]
Comments
Oh, I wish there was something like that in my country.
Which country you in?
I just hope that VPS hosting will become more common in my country so the price can decrease
Pity about the 1mbps connection. It'd be interesting what they could offer with a faster link and some fixed quota per month. I'm guessing data costs in Malaysia are also high like in Australia.
Can you do a traceroute to 119.252.16.253 please? I'd be interested to see if traffic to South Australia is going via the US.
This is common at my country, as bandwidth is costly here.
Here is my traceroute result from the VPS. Interesting, it get throught level 3 US (64.215.29.54)
Sounds like marketing to me
Well,I have other VPS hosted at AIMS,but its from Shinjiru. Though quiet costly,at RM94.90 every month(I add additional IP for RM5). Around USD30.80. Sure is not an LEB. But its still the cheapest I can get with the spec offered.
I get the basic monthly package.
shinjiru.com.my/webHosting/vps/vpsPackages.html
By the time I got this,the bandwidth offer is not 1Mbps,but 100Mbps.
Here my result.
Wow, this is great! Never tried a VPS with 100Mbps in Malaysia. Any limitations for the monthly bandwidth usage?
Sorry to make you think like that. Just too excited for me to find an affordable VPS at my country and share it out
@seikan yes,it's capped, at 250GB.
below is the offer I get at the time for basic package.
Wow, that traceroute is ridiculous... Draw it on a map and you'll go crazy. It's amazing that you can't get routes down to Australia directly via either Singapore or Tokyo... Internet connectivity in South East Asia is so illogical.
maybe that's why it's so expensive...
So sometimes it's kinda useless to use anycast service like cloudflare or else, because net routing in SEA is funny.
This is the result from my traceroute above:
Malaysia => India => Canada => India => United States => Australia
Googled a internet map and found this:
!(http://yangrossman.com/internet-map.gif)
Not bad. The result is actually better than Shinjiru, which routes through AS6453 and got a free trip to HK.
VPSMalaysia
The only sane-routing provider I've noticed in SEA is Softlayer Singapore, sadly.
I'm getting 16 hops to an IP there from the UK.
216.12.210.69, if anyone's interested.
Most of the time it makes more sense to simply host on the West Coast. Mainly because of the price, but also thedarnpeeringtomfooleryinsoutheastasia problem.
@ElliotJ
Actually I'm not so sure about that. It might look OK outside SEA, but among SEA countries the routing/peering can be a mess.
Learn what 'peering' means in Asia.
The following is a traceroute from Hongkong to a Akamai PoP.
traceroute -q1 120.29.145.9
traceroute to 120.29.145.9 (120.29.145.9), 64 hops max, 52 byte packets
1 172.28.2.1 (172.28.2.1) 3.201 ms
2 dsldevice (192.168.8.1) 93.766 ms
3 n112119178254.netvigator.com (112.119.178.254) 12.175 ms
4 n219076122230.netvigator.com (219.76.122.230) 14.397 ms
5 *
6 tenge2-3.br02.hkg05.pccwbtn.net (63.218.254.125) 13.850 ms
7 xe-0.equinix.snjsca04.us.bb.gin.ntt.net (206.223.116.12) 188.551 ms
8 as-1.r21.osakjp01.jp.bb.gin.ntt.net (129.250.3.198) 332.787 ms
9 ae-2.r24.tokyjp01.jp.bb.gin.ntt.net (129.250.3.77) 298.658 ms
10 ae-5.r25.tokyjp01.jp.bb.gin.ntt.net (129.250.3.223) 293.293 ms
11 ae-5.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.170) 294.550 ms
12 120.29.145.9 (120.29.145.9) 291.426 ms
TATA:
Tracing the route to 120.29.145.9
1 if-6-981.tcore1.TV2-Tokyo.as6453.net (116.0.82.86) [MPLS: Label 299776 Exp 0] 164 msec
if-6-995.tcore1.TV2-Tokyo.as6453.net (180.87.180.46) [MPLS: Label 299776 Exp 0] 156 msec
if-6-981.tcore1.TV2-Tokyo.as6453.net (116.0.82.86) [MPLS: Label 299776 Exp 0] 176 msec
2 if-9-2.tcore2.PDI-PaloAlto.as6453.net (180.87.180.17) 152 msec 160 msec 156 msec
3 * *
Vlan3254.icore1.SQN-SanJose.as6453.net (66.198.144.6) 160 msec
4 Vlan507.icore1.SQN-SanJose.as6453.net (209.58.116.22) 164 msec 164 msec 160 msec
5 ae-6.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.12) [AS 2914] [MPLS: Label 301136 Exp 0] 160 msec
ae-7.r21.snjsca04.us.bb.gin.ntt.net (129.250.5.54) [AS 2914] [MPLS: Label 637217 Exp 0] 164 msec
ae-6.r20.snjsca04.us.bb.gin.ntt.net (129.250.5.12) [AS 2914] [MPLS: Label 301152 Exp 0] 160 msec
6 as-1.r21.osakjp01.jp.bb.gin.ntt.net (129.250.3.198) [AS 2914] [MPLS: Label 390104 Exp 0] 272 msec
as-1.r20.osakjp01.jp.bb.gin.ntt.net (129.250.2.165) [AS 2914] [MPLS: Label 781440 Exp 0] 272 msec
as-1.r21.osakjp01.jp.bb.gin.ntt.net (129.250.3.198) [AS 2914] [MPLS: Label 390104 Exp 0] 344 msec
7 ae-2.r25.tokyjp01.jp.bb.gin.ntt.net (129.250.2.93) [AS 2914] 356 msec
ae-1.r22.osakjp01.jp.bb.gin.ntt.net (129.250.2.3) [AS 2914] [MPLS: Label 795991 Exp 0] 320 msec
ae-2.r25.tokyjp01.jp.bb.gin.ntt.net (129.250.2.93) [AS 2914] 412 msec
8 ae-5.r25.tokyjp01.jp.bb.gin.ntt.net (129.250.3.223) [AS 2914] 416 msec
ae-5.r24.tokyjp01.jp.bb.gin.ntt.net (129.250.3.221) [AS 2914] 416 msec 428 msec
9 ae-5.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.170) [AS 2914] 324 msec
ae-4.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.162) [AS 2914] 368 msec
120.29.145.9 [AS 2914] 364 msec
That's pretty good that Softlayer announces it worldwide prefixes to Asia including HKIX. That also helps other ISP's in SEA as HKIX is one of the major IX's in Asia.
Blame PCCW.
Even Three host an Akamai node inside HK and so do others.
Even Three host an Akamai node inside HK and so do others.
PCCW do too, but because Akamai heavily relies on GeoIP, I would only get directed to the right node when I use PCCW's recurrsive DNS servers, which would not return NXDOMAIN but rather their advertiesing page. The traceroute I posted above happens everyday to me, who uses Google's Public DNS. Below happens if I use PCCW's recurrsive DNS:
traceroute -q1 219.76.10.233
traceroute to 219.76.10.233 (219.76.10.233), 64 hops max, 52 byte packets
1 172.28.2.1 (172.28.2.1) 1.068 ms
2 dsldevice (192.168.8.1) 63.455 ms
3 n112119178254.netvigator.com (112.119.178.254) 12.776 ms
4 n219076122250.netvigator.com (219.76.122.250) 13.263 ms
5 pcd101094.netvigator.com (203.198.6.94) 14.137 ms
6 tswc8b233.netvigator.com (219.76.10.233) 12.915 ms
PS: Oops, you seems familar with the CDN thing in Hongkong. Any chance you worked in Hongkong?
I'm getting 16 hops to an IP there from the UK.
The count of hops alone doesn't mean much (or anything), it's just a matter of choice how a particular carrier has their network set up. E.g. with Level 3 you see a lot of those very verbose and geographically informative hostnames of hops on a trace, and e.g. with NTT you see no hops at all between London and Osaka, just a sudden latency jump of +260 msec there (and don't get me started on Russia's Megafon...). So not a lot of hops, but it's actually worse, since you don't know how do they actually route the traffic on that path.