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.
Comments
Oh man this is so tempting with the snapshots now...must...not...spend..more money arrrggh! Moved Wable to the top of my next purchase list
A notice was emailed to clients about snapshots, it can be viewed here;
Snapshots added to Wable, AUTOMATIC SNAPSHOTS HAVE BEEN ENABLED. Please view this COSTS and FEATURES notice; http://wable.com/snapshotsnotice.html (holy capsman)
Sweet! Tempted to grab another bundle to test them out.
Is powerboost also still active?
Yes.
Does Wable have a feature that will shutdown your VPS(es) when a certain % of the bandwidth allocation is reached? I see the ToS states 50 cents a gigabyte for overage -- that could get really expensive if your servers are under a DDoS attack or something.
@Incero did you miss this post?
Bandwidth is currently unmetered.
e: [email protected] if you have any concerns about planned applications on our nodes. Typically our nodes are massively over provisioned with lots of capacity, with no container noise issues.
The user linked above hasn't experienced this and you're failing to defend yourself. It doesn't look good, that's all.
Thanks, just used powerboost! and it works, hahahahaha,
Here are our loads (all machines are way below their CPU counts);
I'm not aware of any ongoing issues. Clients who use more cores than they purchase (e.g. overload) will be notified, and limited if they don't reduce. Clients who use their purchased cores are fine. 1 core = 1.0 load or below.
Specific questions need to be sent in tickets so that we can review your account.
@Incero I sent a sales email into Wable regarding a 'planned application', which in its current state has not used more than 1.4 load, its a single core multi threaded application, and you said you would only allow it on bundle #6 or higher... So if I would not even use more than 2.0 load, why are you saying I need a 12 cpu bundle to run a <=2.0 load application?
Paste the full ticket here and we'll all know why..... I can't magically guess what ticket is yours :-). However if you emailed before signing up, and we thought your application was something that needed more resources, of course we would have told you that. We're very open about asking people not to signup with us if we think their programs will cause abuse, network attacks, etc.
Thanks!
It isn't (or shouldn't) be possible for your clients to steal more CPU time from the host node because they're utilising their allocated cores as you seem to be suggesting.
As you're posting claims here that customers can hit their cores as heavy and for as long they desire, I think you need to look into the individual cases and clarify.
@Incero ticket id is 075804200143207, I don't see the need to paste the full ticket here.
If I required extra resources in the future, I would upgrade. I don't really need someone telling me what resources my application would/may need. I also asked if I could try it on a smaller bundle and if required I would upgrade to a suitable bundle, but you still insisted on bundle #6 or higher from the get go, and you never really explained why a bigger bundle was required, so not really as open as your making out.
If you're on plan 3, don't exceed ~140 units (could be less) of CPU usage for a period of 3 days or you'll get a notification that your VM is declocked to 100 Mhz. Most applications won't do that but it depends on what you're running.
Edit to clarify: 140 units is a measurement that could be done with OpenVZ. To my understanding, 100 units is 100% of 1 core. So 140 is about 1 core and a half.
He told you that it's allowed, showed you that nodes are under control. Even I'm confused about what more you're asking for.
@Jar You can't use 100% of your CPU, regardless if you're on powerboost or not.
Meh, oh well, I love my dedis for CPU intense stuff
Never heard anything about the 100Mhz thing though. I suppose me and Ryan spend more time playing Halo than talking Wable policy though :P
I'm just asking him to look into the cases mentioned here for just a few minutes vs completely overlooking them.
@Incero is claiming customers can use CPU at 100% for sustained periods of time, @black is saying he had his account CPU limited and then his account terminated allegedly for using too much CPU. Now if @black is wrong, surely it's in the best interests of @Incero to look into this case and find out what has gone wrong?
I'm still failing to understand this comment from @Incero.
How are Wable containers managing to consume more CPU than the cores they're allocated?
Ah I see
I mean, you can have one core and a load of 40. We've definitely all been there. So if it's 1 load per CPU core that makes sense then.
0101> @wych said:
Hi @wych, while a little too late for you, we do appreciate your feedback. Feedback helps us build a better service!
RDNS can be set with Bundle #3 or higher, per our FAQ; https://wable.com/faq#faq-20
A 72 hour refund period was also recently added (up to $25); https://wable.com/faq#faq-29
@Incero New York and Seattle seem singlehomed ? any plans on expanding on that
Looked into this after a deal from them on VPSBoard, and ran into some rather... unpleasant Terms of Service. Reposting it here so that everybody is aware of them, copied from the VPSBoard post:
And this one, that I'm fairly sure would just be straight-out illegal in the Netherlands:
EDIT: These are 8 different snippets found in different places in the TOS, but Vanilla seems to be concatenating them together in a single quote block for some reason. They're not continuous in the original; just excerpts.
All looks good to me. You can't please people who obsess over these details and are not providers (meaning they lack the experience behind the decisions), it's just not possible. People who seek to find things to be upset over will always find it.
Have a beer. Most companies will bend their TOS in your favor when they see that it's justified. As long as the TOS isn't like "we reserve the right to break into your home and murder your family."
Hi Joe,
Thanks for the comment. Everything is redundant.
NYC is a single carrier but is on a redundant router fed switch (nlayer/gtt, so when they do router updates they do one, then the other for no downtime), we've had 100% uptime there.
Seattle has;
All locations are using servers with A+B PSUs, fed by A+B PSU from A+B UPS, and redundant generators. We've had 100% uptime on our A+B setups for years.
No expense has been spared in terms of infrastructure.
TOS are a serious matter, especially when it includes terms that go beyond "your service can be suspended or terminated" (as is the case here).
These TOS are quite a bit beyond the 'protective' terms that I've seen at other companies, and it's clearly not boilerplate either.
We appreciate your feedback, a lot. If you're not happy with the TOS we simply ask that you do not sign up. I believe that most customers are comforted by us being in business since 2008 (this doesn't happen without providing stable service), and by our offering of a 72 hour money back guarantee.
Sorry to hear that you wont be using Wable.
I understand that, and that was indeed the decision I've made. I just wanted to make sure that everybody was aware of these (unusual) terms, seeing as most people don't seem to actually read Terms of Service.
No ill will
Is this then a mistake on your website?