Just launched 6x 2GB Vultr KVM VPSes in 6 different location to run my centminmodbench.sh comparison benchmarks like I did here. Since I am developing my own custom GeoDNS based SPDY SSL CDN using Centmin Mod web stack as the core, I thought I'd see how these specific Vultr locations would do Referral links: If you like this comparison review, please consider using my referral links to sign up or put the word out and share this benchmark review with your friends etc : Vultr - offers free $5 credit for new sign ups Vultr KVM VPS Specs 2GB Memory 2 CPU cores 40GB SSD 3TB Bandwidth CentOS 6.5 64 bit Vultr KVM VPS Locations Tested The following 6x Vultr KVM VPS locations were tested: Los Angeles Dallas New Jersey London Tokyo Australia Initial Virgin centminmodbench.sh benchmarks Initial tests are done on a fresh CentOS 6.5 64bit OS without Centmin Mod LEMP web stack. This is to test the systems without any interference from Centmin Mod LEMP web stack's installer and tweaks to TCP etc. I use SecureCRT SSH client which allows sending a single command to all launched SSH windows, so basically I ran centminmodbench.sh simultaneously on all 6x Vultr KVM VPSes, so benchmarks reflect at the same period of time for bandwidth speed and ping results. Tabulated centminmodbench.sh virgin run times. Fastest to completion was New Jersey at 708 seconds followed by Los Angeles at 727 seconds and slowest was Sydney Vultr KVM VPS location at 1,125 seconds. Vultr Disk ioping tests Default ioping performance is pretty much the same across all but one Vultr KVM VPS location - London was nearly half the IOPs compared to other locations and cached IOPs was nearly a third. Vultr Disk dd tests Same trend, all Vultr KVM VPS locations pretty close except slower at Vultr London. Vultr Disk fio tests Again same trend with disk fio performance for random reads and writes being closer on all Vultr KVM VPS locations except London which is nearly half to a third the speed in terms of MB/s and IOPs. Vultr Bandwidth Speed tests Bandwidth download speed tests are geographically relative, so closer the download site to the Vultr KVM VPS location, the faster it is usually. Unfortunately, it seem in the case of Vultr Sydney VPS, while it was the fastest, it wasn't that much faster than some West coast USA locations. Los Angeles, Dallas and New Jersey look pretty good across all bandwidth download locations. Vultr Ping tests Ping times are also geographically relative. Los Angeles does look like a good all rounder though. Vultr OpenSSL Benchmarks OpenSSL system benchmarks test against system default OpenSSL 1.0.1e for number of ciphers and configurations would be good indicators for https SSL performance given Google now includes https in their ranking signal search engine algorithms. Relevant tests include rsa 2048bit, rsa 4096bit and 256bit ecdsa key algorithms. You can read why the newer ECC SSL certificates using 256 bit ecdsa key algorithms are better performing than the more commonly used rsa 2048 bit keys here. As well as test aes128/256 cbc non cpu hardware assisted performance and AES-NI cpu hardware assisted performance via the evp aes128/256 numbers. Again looks like Vultr London VPS performance is lagging behind the rest at less than 1/4 of the performance compared to the rest of the other Vultr locations. Best rsa 2048/4096 bit performance goes to Vultr Tokyo followed by Vultr Dallas, New Jersey, Sydney and then Los Angeles with London at last place. There's a change in leader board when it comes to 256 bit ECDSA signatures with New Jersey falling behind at almost 1/2 the performance for signatures and verifications. London again came last though. hardware assisted AES-NI aes128 and aes256 performance has Vultr Tokyo in the lead again and Vultr London last.