New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Vultr Long Term Reviews
Considering Vultr as a replacement for DigitalOcean for a large Elasticsearch cluster due to their larger ram, and their large disk based storage tier.
Anyone been using Vultr, Netherlands PoP long term? Got any reviews in regards to stability & performance etc?
Additionally has anyone been using large amounts CPU/IO for long periods of time and had any issues? Are they like DigitalOcean and just throttle/schedule a bit or is a suspension more likely?
I couldn't see it in the API documentation, is anyone aware of any way to determine the Physical Node you are located on? Its actually fairly important for distributed systems with built in redundancy.
Comments
I can only answer 2.
They are really cool about large amounts of CPU/IO for long periods of time. I used to stress their servers a LOT, and they never complained.
I'm using Vultr from the start and they're stable not exactly %100 but ~%99.
CPU abusing is ok but I/O you'll be throttled. Probably they're not using even RAID and that's a reason why they're slow in terms of constant I/O.
Probably you should create a ticket and ask? Haven't used API myself, so don't know.
Smell benchmark:
Amsterdam is now multihomed.
HOST: server Loss% Snt Last Avg Best Wrst StDev 2.|-- border1.tshr.melbourne.co 0.0% 10 0.4 0.3 0.2 0.4 0.1 3.|-- no-ptr.as20860.net 0.0% 10 0.7 0.8 0.7 1.0 0.1 4.|-- 3505.core1.dc2.as20860.ne 0.0% 10 6.6 6.5 6.4 6.8 0.1 5.|-- 250.core1.hex.as20860.net 0.0% 10 6.7 36.5 6.6 145.0 56.6 6.|-- ae5.lon25.ip4.gtt.net 0.0% 10 6.6 6.7 6.5 7.3 0.2 7.|-- xe-11-1-1.lon11.ip4.gtt.n 0.0% 10 15.1 15.1 15.0 15.5 0.1 8.|-- as2914.lon10.ip4.gtt.net 0.0% 10 13.0 13.2 13.0 13.5 0.2 9.|-- ae-7.r23.londen03.uk.bb.g 0.0% 10 7.3 8.3 6.9 11.2 1.7 10.|-- ae-3.r22.amstnl02.nl.bb.g 0.0% 10 41.4 24.3 12.8 49.4 14.9 11.|-- ae-1.r02.amstnl02.nl.bb.g 0.0% 10 13.8 13.7 13.5 13.9 0.1 12.|-- ae-4.r00.amstnl03.nl.bb.g 0.0% 10 13.0 14.6 12.8 21.6 2.5 | `|-- 129.250.6.69 13.|-- 81.20.72.122 0.0% 10 13.2 13.7 12.4 18.2 1.7 14.|-- 108.61.198.102.vultr.com 0.0% 10 13.4 13.6 12.5 15.8 0.8That's NTT and Level3 at the minimum.
This isn't something the API covers however @DaveA has told me in the past it's unlikely a VM will be deployed on the same host node even when deployed in quick succession. You could probably submit a ticket after deploying and ask about that.
They don't disclose any RAID configurations, @DaveA has made off record comments that they're using some level of redundancy.
I'm dumping vultr at the moment. their API is broke.
You can forget getting a response from them on the issue either.
I'm done with those fools.
Vultr do have RAID setups.
Sauce?
Sources please? Vultr has (as far as I know) never released any information about their RAID setup. There was a topic about it a while ago, they tried everything possible to avoid answering questions about whether they use RAID or not.
They don't have any RAID, some level of redundancy is backups on host node. That's nothing in terms of speed and reliability!
I have a couple of servers in The Netherlands at Vultr, it's pretty good. Fast servers and 100% uptime as far as we have seen (they aren't production servers so we don't use Pingdom or anything).
As for suspension, etc., well, I have never experienced that myself; so I can't answer that.
Are you actually seeing any issues where the IO Vultr provides isn't sufficient for your use case or are you just spinning fanboi hype?
Vultr deleted account of my client twice and refused to reactive it nor to take backups after they got complains about spam (website hacked).
If your account is receiving multiple complaints regarding activities such as spam, then I wouldn't expect them to do anything else. Good on them.
vultr backup sucks sooo bad.
You can only go back 2 days.
I have been using service for a few months now. Rock solid in chicago can't comment on Netherlands.
Bad news is they have been degrading service. When I first started they advertised 3+ cores. They recently reduced this to 2.4. My current server with them is running 3.6. I did some unixbenchmark test with my running server vs new build. Performance was 2179.8 on old running server, clean server showed 1422.8. This was a 768m chicago server BTW
Today it also looks like we are being hit with price increase!
Needless to say I am looking for a replacement!
Dave said in IRC
@nightshade - when did those price increases take effect? They now seem to be the same price as DO and Linode for anything 1 GB or above. Except they have the 20% sale. This is the old grocery store pricing strategy - up your base price, then lower it with a sale. Then terminate sale down the road and hope the price increase sticks.
I think sometime today.
Thinking Choopa is wanting out of the vps business. They clearly don't want to compete anymore.
They're spending millions revamping their product right now, improved locations and new hardware etc. They're still working to bring the storage product to more locations.
You couldn't be more wrong.
I am sure they did the cpu drop to save money. Can't say I blame them but this was one of the main selling points that set Vultr apart from DigitalOcean. (Guessing this is vultr biggest completion) This is what finally got me to move my server off DO. If I was looking today I would pass up Vultr.
You top that with what a 30%+ price increase on at least the lower end servers (before discounts) not a good way to revamp brand. Not sure how much the sata storage plans when up that happened a couple of weeks ago.
@nightshade - it may also be that they were using up bulk of old servers which were higher speed than the ones being used now.
With you hanging around all day together with DaveA in a semi-private IRC channel, it seems as no wonder that you are his private spokesman now.
Or is it semi-public?
Whatever you call it.