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
就是不告诉你
the most of is CPU
RamNode suspend your vps way before you hit any CPU limits, so go for the Standard plans.
What don't you want to tell us?
That "0.9 of a core"-rule while selling access to up to 4 cores always gave me an unsafe feeling with their generally great service. So I moved away and never looked back.
The AUP has been updated a bit since to be more specific
I've been considering picking up another machine from RamNode as well, but I'm also not sure between the Premium and Standard plans. Aren't E5's better than E3's? Or does the clock speed have a greater impact with this type of thing?
Mind telling us who gives unthrottled cores and allow you to use them all the time except Abusive Cores?
Faster clock speed means faster processing, but it also depends on what you are running on your VPS.
Pretty much nailed it. I don't see why having a limit in the AUP as a bad thing, it helps them deal with people who abuse their VPSes and affect other clients.
It's not about doing this 24/7. But Prometeus, for example, are way more relaxed.
Example:
http://i.imgur.com/dpaJXP0.jpg
Not doable with Ramnode,but doable with Prometeus. Note that the munin graph does not show a Prometeus VPS, but the same usage was no problem there.
They throttle the vCPUs. Try again.
Well, @Maounique can surely clarify this. I had no problems during the time I used them for the specific site with high CPU usage from time to time over several hours. With Ramnode, I always was in fear that they could suspend my VPS because of that passage in their AUP.
btw the standard plans aren't available in NL
@Nick_A why is the NL location not available for the standard plans?
And I was planning to post an ad here today...
@Amitz - Am I right in understanding that you left out of fear of the hypothetical without actually experiencing problems? Or did you receive a bunch of warning tickets?
@tr1cky - I'm pretty sure we've been over this before, but that's not accurate. You would be seeing hundreds of people running around complaining if that were the case. I realize you had a bad experience (or your client did? I can't remember), but that's not enough to start generalizing so broadly.
E5s have a somewhat slower clock speed than E3s; however, I doubt many people actually notice the difference since we are talking 2.6GHz on almost all of our E5 nodes (E5-2630v2). Most of our "slow" stuff is faster than the performance lines at other hosts. The E5s are just a better system to be able to offer more disk space than our E3s. If you're running a Minecraft server or something similar, you need to go with an E3. Pretty much everything else will run great on our E5s.
Still working on it.
Actually all existing OpenVZ plans were changed in that manner. Extra space, less vswap basically. Existing VPSs were given the extra space for free (minus the few with custom plans or those on really old plans as explained in our recent News posts).
@Nick_A: Indeed. And I am sure that I am not the only one. That clause can make people with sporadical peaks over some hours become nervous to have their VPS suspended while being away from Internet access. I enjoyed your service overall, but that Damocles Sword in your AUP felt bad.
Did you open a ticket or contact us to work through it? Many people have and have come away satisfied. It sounds like you left without verifying whether your fears were well founded or not, which is unfortunate to say the least.
RamNode never suspended me because I used to much CPU. They notified me, or they rebooted my server, or they stopped it and notified me.
My CPU usage is the least i'm worried about.
I think they've said they don't throttle OpenVZ?
Anyways, I personally don't fault providers for imposing CPU limits -- I just don't like RamNode's way of doing it because it doesn't scale at all based on the number of vCPUs your plan has. Before I saw your post here I was actually going to point to the way you do it with VPSDime as a better example. Even though all your plans have 4 cores, the limit's at least based on that number.
I opened ticket and @Nick_A solved it very fast
I was just warned, but my vps was not turned off or suspended after accidentally having many hours of heavy cpu.
How many hours of how heavy CPU usage if I may ask?
At least 8 hrs @Amitz
Thanks! How much CPU did you use during that time (in cores)? I am evaluating whether I use RamNode again and that information would be highly appreciated! @jcaleb
But they told me to fix it anyway, and I did. It's just a cron job that went wild. I still think they wont allow cpu abuse. But in case of accidents, I think they will give you a change to fix it.