Linode switches to hourly billing with monthly caps...
- Thread starter Abydon
- Start date
Any idea how the cpu speed of their "8 core" 0.24/hour server compares with an E3-1245v2?
Uptano.com has something comparable to the Linode offer but that's an actual single tenant server, that seems more attractive. However, it's apparently a dual L54xx so it's only about the same speed as a midrange E3.
Uptano.com has something comparable to the Linode offer but that's an actual single tenant server, that seems more attractive. However, it's apparently a dual L54xx so it's only about the same speed as a midrange E3.
http://incero.com/ <-- check here for better prices 
Long story short, the linode idea is sound because you can spin up a server during peak loads, and then kill it during lower usage times. You get a good network spread, so it isn't that bad. I also assume you can load up a prebuilt image.
Mun
Long story short, the linode idea is sound because you can spin up a server during peak loads, and then kill it during lower usage times. You get a good network spread, so it isn't that bad. I also assume you can load up a prebuilt image.
Mun
Ruchirablog
New Member
open a ticket asking for a migration. They will happily do that for you
Dylan
Active Member
It's funny you linked Incero because: https://wable.com/http://incero.com/ <-- check here for better prices
Not really all that surprised - really all one needs to enable hourly billing is a control panel (for both billing and VPS control) that supports it. Linode's control panels have always been custom.
lbft
Active Member
Hourly billing does present a different usage pattern though - for one thing, when people spin up servers on-demand it usually means they want to use a lot of a particular resource right then, affecting how hard you can oversell. Also if people can spin up new instances for a couple of hours/days to cover peak usage then maybe they won't upgrade to a higher plan as soon.
Of course lots of people are just going to spin up instances and keep them running permanently (because automatically deploying instances is harder than just setting them up manually once), and some number of people are going to sign up because if they cancel it after a day or two they're only out a couple of bucks, so the marketing benefit may outweigh the downsides.
Of course lots of people are just going to spin up instances and keep them running permanently (because automatically deploying instances is harder than just setting them up manually once), and some number of people are going to sign up because if they cancel it after a day or two they're only out a couple of bucks, so the marketing benefit may outweigh the downsides.