After some rather heated exchange with William from Edis, where he:
- gave no explanation
- yelled at me in CAP and bold
- showed a lack of understanding of the slash notation (e.g. 192.168.1.100/24)
I went around Edis and poked the data center, and the matter was mystically resolved shortly after.
Besides, I also experienced an unscheduled and unannounced downtime once in my short time with them. These things only happen with low end VPS providers, and of course AWS EC2.
~$ uptime 23:47:12 up 750 days
Otherwise, I got all that was promised, 1 IPv4, IPv6 /112, it seems to be a 2533MHz 5066 bogomips amd64 thingy, but no idea how many others are sharing. I'm running Debian on it, basically just providing OpenVPN for my computers/devices.
Their management UI is quite barren and happily mixes German and English, so I'm not quite sure of all its features...
If your budget allows 7.9 euros, http://www.hetzner.de/en/hosting/produkte_vserver/vq7 is probably a nigh bit more reliable (according to a colleague, who has exactly that).
I also had a Linode's 512M, comparing the two Linode wins on reliability and management features. But at 14 GBP (what, ~22 dollars?) you can get a dedicated server from http://www.kimsufi.co.uk/
But if all you need is a ton of bandwidth and space (1tb!), it's a nice deal. They have great connectivity (located in France), and only went down for one evening (when all of OVH network went down simultaneously worldwide).
For more power and CPU usage, you're better off with an VPS. They usually also have RAID underlying drives so at least you have some more warranties against data loss.
VIRT memory limiting is very a serious issue for some software. For example, apache may use 10x VIRT memory because it is threads-based (most linux'es reserve about 6-10M VIRT memory for the stack of each thread). VIRT memory is usually considered "free to allocate" and software (JVM, soft that uses mmap and so on) is written with this assumption. But this is not the case with OpenVZ VPS servers. Just run "top" to get an idea about VIRT and RSS memory usage of common programs.
It is exciting how this issue is not well-known. I even think that 91.318% of "apache is memory hungry" things (they are still partially true, but..) came from OpenVZ VPS benchmarks.
So in my opinion 20$ 512MB XEN is way better than 10$ 512MB OpenVZ because 512MB XEN is very different from 512MB OpenVZ.
P.S. my knowledge of OpenVZ may be outdated because I moved from OpenVZ VPS servers a couple of years ago.
This is still true for OpenVZ. You can't really run JVM or SBCL on OpenVZ VPSes for that reason.