The New Linode Cloud: SSDs, Double RAM and much more
blog.linode.com
blog.linode.com
Because Linode treats their servers like kittens (upgrades, addons/options, support), and DO treats their servers like cattle. There's nothing wrong with the cattle model of managing servers. But I'm not using Chef or Puppet, I just have one server that I use to put stuff up on the internet and host a few services. And Linode treats that one solitary server better than any other VPS host in the world.
(1) I do have one DO box as a simple secondary DNS server, for provider redundancy
I'm not sure "disposable" is a good word to describe DO's approach. We do know that they cram a lot more people per host machine, though. That may be where the "treat VMs like cattle" statement was getting at.
You need only fire up a few instances of comparable type, get some CPU load, and watch some basic metrics to determine this for yourself.
OTOH the lowest ($20) tier on Linode is probably used by more serious projects that, on average, exert considerable load.
I'm not sure about that. For me, I pay the extra few bucks on Linode for the customer service, stability, and the consistent performance. I'm not running my VMs ragged, I'm just willing to pay a little more for a higher quality service.
Anecdotally, it's a quality thing for me. Digital Ocean = Economy car, Linode = A nice Hyundai sedan or a higher end Accord.
I was with Linode and had to deal with constant outages (at Fremont DC) and went through two major hacking incidents where I found out through Reddit instead of from them. I've never been with a worse provider than Linode.
That being said, I do think they're great value, and I have a reverse bidding dedicated server from Hetzner, that I use as a test and staging server. But I wouldn't dream of using them for production instances though - for the amount you'd have to pay to beef up support and get access to things like out of band console access, you might as well pay for a server from Bytemark.
> If you some evidence that DO is inferior at the same price level as Linode then you should post it.
I don't care to do this, I'm not out to prove anything. I'm here to share my experiences. Take them or leave them, I don't care either way.
If you are using DO and you like it, then stick with it. I've personally been happy with DO (for the price), but feel like you get what you pay for in this regard. Sometimes over-provisioned host machines, erratic network and disk IO, frequent maintenance windows, slow and hurried customer service.
I use DO for this and have used many others in the past and I have never had any problems with DO...
Also, stolen CPU on my DO boxes is super high, whereas this is very rare on Linode. You have less neighbors.
I have put this down to the DO SSDs. It will be interesting to see if this is true. I've been considering migrating from Lindoe to DO because they were faster and cheaper.
I've had 2 DO VPS for about 6 months, and never had a problem with them.
Faster how? This doesn't tell us anything.
> I have put this down to the DO SSDs
Linode now uses SSDs, too. And server-grade ones at that.
With 3 out of 4 outages or 'troubles' at Digital Ocean, there is no report on there status page. Even when tens of people complaining about it on twitter and they replied on the tweets that they have an outage, there is nothing on the status page.
So I would not recommend comparing there status pages.
however, I have no experience with Linode so I can not say if they are "kittens" as you say.
I was however happy to have a viable alternative to Linode. I found their handling of the two hacking incidents to be completely disrespectful to me as a customer.
$ dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 1.31593 s, 816 MB/s
$ hdparm -tT /dev/xvda
/dev/xvda:
Timing cached reads: 19872 MB in 1.98 seconds = 10020.63 MB/sec
Timing buffered disk reads: 2558 MB in 3.00 seconds = 852.57 MB/sec
Upgraded cpuinfo model: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHzOld cpuinfo model: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz
CPUs compared: http://ark.intel.com/compare/75277,40201
dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1,1 GB) copied, 13,6791 s, 78,5 MB/s
hdparm -tT /dev/xvda
/dev/xvda:
Timing cached reads: 3580 MB in 2.00 seconds = 1794.00 MB/sec
Timing buffered disk reads: 336 MB in 3.01 seconds = 111.75 MB/sec $> dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 2.19598 s, 489 MB/s
$> hdparm -tT /dev/xvda
/dev/xvda:
Timing cached reads: 12446 MB in 1.98 seconds = 6273.29 MB/sec
Timing buffered disk reads: 1768 MB in 3.00 seconds = 589.00 MB/sec dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 2.17496 s, 494 MB/s
hdparm -tT /dev/xvda
/dev/xvda:
Timing cached reads: 18560 MB in 1.98 seconds = 9358.78 MB/sec
Timing buffered disk reads: 2510 MB in 3.00 seconds = 836.61 MB/sec` # dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 3.7375 s, 287 MB/s
# hdparm -tT /dev/disk/by-label/DOROOT
/dev/disk/by-label/DOROOT:
Timing cached reads: 16394 MB in 2.00 seconds = 8205.62 MB/sec
Timing buffered disk reads: 868 MB in 3.00 seconds = 289.17 MB/sec 287 MB/sec / $5 ~ 57 MB/sec/dollar
816 MB/sec / $20 ~ 40 MB/sec/dollar 287 MB/sec / $20 ~ 14 MB/sec/dollar
I don't think MB/sec/dollar makes sense simply because disk speed does not scale. If you need a (very) fast disk, Linode is obviously the better choice.I upgraded some of my VMs and they all failed to boot on their own and I had to manually boot each one after the migration.
[root@server ~]# dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 6.29244 s, 171 MB/s$ dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 5.83509 s, 184 MB/s
1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 62.9023 s, 17.1 MB/s
$ dd bs=1M count=40960 if=/dev/zero of=test conv=fdatasync
40960+0 records in
40960+0 records out
42949672960 bytes (43 GB) copied, 48.455 s, 886 MB/s(Okay Linode, you've finally done it. I'll get rid of my oddball $30/mo plan sometime soon. That extra $10 used to get me a necessary 180MB of extra RAM!)
dd if=/dev/zero of=test bs=512 count=1500 oflag=dsync
I'm getting "6.40264 s, 120 kB/s" on my laptop's SSD, but on a proper server with a RAID card and cache enabled I get "0.187033 s, 4.1 MB/s".
768000 bytes (768 kB) copied, 0.45329 s, 1.7 MB/s
$ dd if=/dev/zero of=test bs=512 count=1500 oflag=dsync
1500+0 records in
1500+0 records out
768000 bytes (768 kB) copied, 0.427272 s, 1.8 MB/s $ dd if=/dev/zero of=test bs=512 count=1500 oflag=dsync
1500+0 records in
1500+0 records out
768000 bytes (768 kB) copied, 1.64471 s, 467 kB/s 1500+0 records in
1500+0 records out
768000 bytes (768 kB) copied, 1.17399 s, 654 kB/s[Edit: Removed the bit about DigitalOcean Plans. If you have Ghostery running, it apparently takes out the html block listing different plans]
I'd really like to know the results of the test.
That said, I am not an expert on CPU virtualization but I did notice that the new plans are differently phrased than the old ones here. The old plans all talked about 8 CPU cores with various 1x, 2x priority levels (https://blog.linode.com/2013/04/09/linode-nextgen-ram-upgrad... for examples), while the new plans all talk about 1, 2, etc. core counts.
Could anyone with more expertise here tell me whether this is a sneaky reduction in CPU power for the lower tiered plans, or just a simpler way of saying the same thing as the old plans?
If you take the upgrade, you inherit the new plan specs, vcpus and all.
We’ve greatly reduced the contention on these new machines compared to our old structure, and in testing this new arrangement provides much more consistent CPU time with less potential for steal. We think it’s great and totally worth the move, otherwise we wouldn’t have done it. These machines are incredibly fast, faster procs, SSDs, the network is incredible, etc.
(Just to be clear, Digital Ocean works the same way. They're charging you for the resource allocation and associated maintenance. If you choose to not actually use the allocation you're paying for, that's your business.)
Sure you'll save some money, but you might also waste hours of your time setting up a server that could one day disappear into thin air.
As an aside, one of my friends has a 100 meg free VPS from one of the terrible free vps providers. He has managed to squeeze a Minecraft server on, and that can hold about 2 or 3 players! (apart from the terrible network, cpu and uptime)
A database server or similar wouldn't work, of course.
1GB-YEARLY
3 vCores
1GB RAM
512MB vSwap
50GB RAID10 Disk
1TB Outbound BW
1 IPv4 and 1 IPv6
OpenVZ/SolusVM
[1] http://iniz.com/[2] http://lowendbox.com/blog/iniz-yearly-deals-and-more-25year-...
1. It's 20 bucks... take a gamble!
2. The owner, Tim, has personally responded to every issue I have ever had within an hour. Pretty stellar, if you ask me.
How big is that market, really? I keep a small VPS around for whatever (I like Hetzner), and I'm sure lots of nerds are the same. But for any usage that's even a little bit serious, $20/month is peanuts.
A lot people don't need an entire server and just need a shell, some file space, and a small web/app server.
Even just 10 years ago it was very expensive to get a non-shared hosting account. Go back a little further than that, and you were elite if you had a real server out there somewhere. Back then a low-spec co-located server was $300 a month. And let's not even talk about how expensive bandwidth was!
I've always needed memory more than disk. Really wish I could pay some of these providers just for a one off increase of a few extra gigs of memory without tiering up which includes an entirely higher level of storage that I will not ever use.
I run a service that could get away with only 8GB of RAM, but definitely needs at least 2TB of space, plus plenty of room to grow.
WholeSaleInternet for example, currently has a Quad-Core Xeon E3 1230 for sale at $49/month with 5 IP Addresses. 1GBPS connection with 10TB bandwidth with 8GB of RAM / 250GB of Hard Drive.
If that 2TB Hard Drive is really needed, you can compromise on the CPU and go for a consumer-grade AMD Fx-4100 (Quad-Core AMD) from Datashack for $55 / month, with 5 IP Addresses, 8GB RAM / 2TB of Hard Drive space, 10TB of Bandwidth on 1Gbps
Most web applications seem to be Disk heavy or RAM Heavy... I rarely see CPU-heavy applications. So the AMD Fx-4100 can be good enough (its far far better than an Atom, although it isn't as good as a modern E3 Xeon).
I've never had the need for it, but since Dedicated Servers often come with 5 or 13 IP Addresses, and they can be as cheap as ~$60/month realistically... I think its better to just install Proxmox on a single dedicated box and spin up your own private VMs if you are honestly going to need multiple VMs.
Linode allow you to attach additional IPs to your Linode at $1/month, for example, I have one Linode which has 6 IPs attached for only $25/month. I still can't find a company has this kind of flexibility.
23.23.23.24
23.23.23.25
23.23.23.26it's called "skin in the game", and those with very little skin in the game do not truly give a shit about their own problems, so they expect others to give a shit for them.
every business learns this lesson at some point. basically all these cheap hosting providers are trying to make money by automating the problem away - we'll see how it works in the long run for hosting. the jury is still out if you ask me.
Yes, this, the $10 plan is DO's most popular.
(Please don't say it's because the pricing page highlights the $10 plan ass "most popular". You know that's just a classic up-sell trick, right?)
1) I feel like Linode offers a level of support that the others don't offer. There are lower end providers that do offer good support, but it's not as consistently good as Linode. Were they to start offering cheaper $5 or $10 a month plans, they would be challenged when it comes to continuing to offer that level of support.
2) Observationally, it seems to me that Linode customers on average tend to be more serious about their usage than those who are looking for a <$5/month VPS. Go to the IRC channels for each company and see who hangs out there. That said, this should only matter to you if you are concerned about who your neighbours may be on a VM host, if you plan on being part of the IRC community, or if you are concerned about how reputable your IP address looks given what block it belongs to.
That said, I do think the performance of DO is quite good. It reminds me of Slicehost back in the day.
The BuyVM guys are just the best people ever, and I mostly maintain play boxes there just b/c I can get away with stuff there that might not fly at DO or Linode.
As a more established provider, Linode has to decide if adding more customers would be worth the incremental support costs. Given Linode's reputation for support, adding a bunch of LEB customers who aren't likely to renew at the same rates as people who pay more money - and are also likely to have more support requests - competing with that market doesn't make a ton of sense.
Plus, whether fair or not, having a minimum pricing point makes a service seem more premium -- more "ready for serious business." Now, obviously we've all been with expensive hosts that have terrible performance -- but you'd be surprised how many non-technical decision makers will choose a higher-priced offering over a lower-priced offering, on the supposition that "more expensive = better."
for $7 you get: 2 cores 2GB RAM
for 10$ you get: 3 cores 4GB RAM
They don't have SSD, but SSD doesn't do everything, I prefer more ram.
EDIT: If some of you don't know OVH, it's because its new in America, but its not some cheap company, it's a European company that is very successful there. And just recently created a datacenter in North America. (I used to live in France, and have known them for some years).
_04/17/2014 - VMPLAN - DATACENTER - OS - AUTHOR_
```
CPU model: AMD Opteron(tm) Processor 4284
Number of cores: 2
CPU frequency: 3000.000 MHz
Total amount of RAM: 2048 MB
Total amount of swap: 128 MB
System uptime: 14 days, 13:31,
I/O speed: 75.4 MB/s
Bzip 25MB: 7.44s
Download 100MB file: 13.0MB/s
``` ```
CPU model: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
Number of cores: 2
CPU frequency: 2800.050 MHz
Total amount of RAM: 1993 MB
Total amount of swap: 511 MB
System uptime: 0 min,
I/O speed: 811 MB/s
Bzip 25MB: 4.93s
Download 100MB file: 19.1MB/s
``` _04/17/2014 - VMPLAN - DATACENTER - OS - AUTHOR_
```
CPU model: AMD Opteron(tm) Processor 4386
Number of cores: 4
CPU frequency: 3100.000 MHz
Total amount of RAM: 3943 MB
Total amount of swap: 1998 MB
System uptime: 10 days, 2:25,
I/O speed: 169 MB/s
Bzip 25MB: 5.34s
Download 100MB file: 15.8MB/s
```BuyVM 128MB ram, 15GB disk, 15USD/year
CPU model: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz
Number of cores: 1
CPU frequency: 2266.746 MHz
Total amount of RAM: 128 MB
Total amount of swap: 128 MB
System uptime: 39 days, 22:35,
I/O speed: 89.9 MB/s
Bzip 25MB: 12.89s
Download 100MB file: 50.0MB/s
QuickPacket: 128MB ram, 20GB disk, 15USD/year CPU model: Intel(R) Xeon(R) CPU X3470 @ 2.93GHz
Number of cores: 1
CPU frequency: 2933.228 MHz
Total amount of RAM: 128 MB
Total amount of swap: 128 MB
System uptime: 48 days, 6:07,
I/O speed: 129 MB/s
Bzip 25MB: 6.40s
Download 100MB file: 1.14MB/s
A good aggregator for low-end deals is lowendstock.com .So a single OpenVZ VPS is actually running on resources which are shared with another VPS box. Mostly the burstable resource is the RAM which is borrowed from another VPS box when its not in use and your VPS box needs it.
On the other hand, KVM is hardware virtualization. The main OS simulates hardware for another OS to run on top of it. It fairly distributes all the resources. It does not have burst resources but it guarantees the dedicated resources. Essentially this means the plan which you see its 100% with you and is never shared with anyone. This also means on load you will not get extra ( burstable ) RAM out of it.
Guaranteed streamline performance is observed in KVM but value per dollar and efficient use of the complete hardware is observed in OpenVZ.
tl;dr :
OpenVZ is OS virtualization. Resources are variable and are shared with other(few) users on the same server as and when required. Dedicated resources are guaranteed but they could be shared with others and your box can borrow when others are idle.
KVM is hardware virtualization. All the resources are dedicated to you and only you. None is shared nor you get the shared bonus if required to your server. Dedicated resources are guaranteed.
Before Upgrade:
Running 30s test @ http://...
5 threads and 20 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 308.91ms 135.01ms 985.82ms 80.00%
Req/Sec 14.15 4.61 24.00 66.36%
2206 requests in 30.00s, 28.51MB read
Requests/sec: 73.53
Transfer/sec: 0.95MB
After Upgrade: Running 30s test @ http://..
5 threads and 20 connections
Thread Stats Avg Stdev Max +/- Stdev
Latency 321.74ms 102.45ms 957.74ms 87.32%
Req/Sec 12.02 2.18 17.00 80.75%
1858 requests in 30.01s, 24.03MB read
Requests/sec: 61.92
Transfer/sec: 819.98KBhttps://news.ycombinator.com/item?id=7564764
Now it's obvious what Linode's answer to that question is: Lower "burstable" CPU for lower plans.
The $20 plan used to be able to burst to 8 cores for short periods, but now it only has access to 2 vcores. The "guaranteed" processing power is probably higher with the newer CPUs, but at the expense of short-term burst performance.
Another minor detail that I find interesting is that the transfer cap for the $20 plan has been increased to 3TB, whereas the $40 plan still gets 4TB. Apart from the transfer cap plateau-ing at the extreme high end, this is the first time that Linode has broken its 11-year-old policy of "pay X times as much money, get X times as much RAM/disk/transfer".
In a virtualized environment, the number of "CPUs" you can see is probably not a great way to measure how much computing power you have.
https://blog.linode.com/2014/04/17/linode-cloud-ssds-double-...
IO is probably more important for most of the peoples who use VPS, but It would be good to see CPU test from others too, not just IO benchmarks.
[1]: Amazon charges $2 an hour thats about $1500 a month.
http://www.nvidia.com/object/gpu-cloud-computing-services.ht...
I'm told that's just the beginning of security faults in their platform, attributable to being a younger company and discovering these things for the first time; I have been personally shown evidence that DigitalOcean's platform initially trusted a hidden field called "userid" and allowed a user to operate on any other user without authorization, including restoring images, shutting down droplets, and so on. Their system at first had no protection against spoofed packets exiting a droplet, either, so ARP poisoning the gateway was (and possibly remains) a viable attack.
Linode is far more mature, obviously.
Every provider has security issues. It's how they rectify and move forward that should concern you. Watching DigitalOcean react to being informed that the issue they got burned on once had reappeared basically told me to never use their services.
Also, and I actually consider this very important and not a grammatical nit, Linode doesn't sell droplets. They sell virtual servers. You're asking for a Pepsi from Coca-Cola. You might consider this a minor nit, but it's actually a serious confusion issue that I already see happening.
Allow me to promise you -- not predict, promise -- that DigitalOcean will be compromised just as badly. It's going to happen. It's a matter of when and how they react.
I didn't mean to use the word "droplet," so I'm sorry for the confusion.
The issue was with how they handled the public disclosure of the hack. Instead of immediately alerting their clients that there has been an issue (so that - as you say - people could take mitigating actions) they stalled on giving information and tried to cover up the whole fiasco. This should give people ZERO confidence in their moral integrity.
If you run a service like Linode or DO, you need to provide certain guarantees on disclosure of security failures and maybe get an externally audit from time to time.
But it's exactly one year since the hack and everyone is back to talking about how amazing Linode is
http://news.softpedia.com/news/Hackers-Claim-to-Have-Gained-...
Before
-------
CPU model: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz
Number of cores: 8
CPU frequency: 2266.788 MHz
Total amount of RAM: 988 MB
Total amount of swap: 255 MB
System uptime: 8 days, 12:03,
I/O speed: 69.9 MB/s
Bzip 25MB: 8.96s
Download 100MB file: 47.2MB/s
After------
CPU model: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
Number of cores: 2
CPU frequency: 2800.086 MHz
Total amount of RAM: 1993 MB
Total amount of swap: 255 MB
System uptime: 2 min,
I/O speed: 638 MB/s
Bzip 25MB: 5.10s
Download 100MB file: 146MB/s
Test: https://github.com/mgutz/vpsbench CPU model: QEMU Virtual CPU version 1.0
Number of cores: 1
CPU frequency: 2299.998 MHz
Total amount of RAM: 491 MB
Total amount of swap: 0 MB
System uptime: 276 days, 5:04,
I/O speed: 253 MB/s
Bzip 25MB: 7.83s
Download 100MB file: 56.0MB/s
Here is Vultr's $5/month plan: CPU model: Vultr Virtual CPU 2
Number of cores: 1
CPU frequency: 3399.994 MHz
Total amount of RAM: 490 MB
Total amount of swap: 509 MB
System uptime: 28 days, 3:15,
I/O speed: 485 MB/s
Bzip 25MB: 3.17s
Download 100MB file: 58.2MB/sI get I might not be their target market (small business with about $1000/month on IaaS spending) but there are a couple things preventing me from doing so: 1) $10/month size suitable for a dev instance. 2) Some kind of scalable file storage solution with CDN integration – like RS CloudFiles/Akamai or AWS S3/Cloudfront or block storage to attach to an individual server.
I guess you get what you pay for… infrastructure components and flexibility AWS > RS > Linode > DO which roughly matches the price point.
Unlike Amazon, you don't have any good options for increasing your storage space on Linode using network block storage, unless you somehow run another Linode and NFS them together. Being able to launch a moderately priced server with hundreds of gigs of spinning rust on AWS is still a nice option to have.
I stopped being a customer since migrating to DO but my needs were really small
But I think their strategy of keeping the price and increasing capabilities are good. Between $5 and $20 is a "big" difference for one person (still, it's a day's lunch), for a company it's nothing.
However, I would definitely go to Linode for CPU/IO intensive tasks. Amazon sucks at these (more benchmarks between the providers are of course welcome)
What is the difference between the 16GB - 96GB Plan and a dedicated server? And why would i pay 3x the price? The advantage of those who offer Cloud / VPS and Dedicated Servers Hosting company is they can mix and match depending usage. If you are actually building an any sort of infrastructure with Linode those large box are extremely expensive.
But here is one thing that DO provides and I think Linode too should, you get the choice to spin up a $5 instance anytime in your account for any small project or a test instance which you cannot on Linode.
Linode's announcements usually come in triples...I'm excited for number three. Let's hope its some kind of cheap storage service.
Long version: "If you take the upgrade, you inherit the new plan specs, vcpus and all.
We’ve greatly reduced the contention on these new machines compared to our old structure, and in testing this new arrangement provides much more consistent CPU time with less potential for steal. We think it’s great and totally worth the move, otherwise we wouldn’t have done it. These machines are incredibly fast, faster procs, SSDs, the network is incredible, etc."
From Caker's comment on the blog. It seems that this was done to reduce fighting over core and provided more consistent fair availability of processing power when they tested it b/t VMs.
For example, my VMWare server is a single 8 core processor, but my VM's only see 2 cores, as that's the way I prefer it and I believe VMWare recommends this or even one core. Those 2 virtual cores can access all 8 physical cores.
The only real way to find out your cpu performance is to run a benchmark.
However it is advisable to minimize the vCPUs in VMs because it greatly enhances scheduling -- if a VM has 8 vCPUs allocated to it, with some hypervisors that lack advanced co-scheduled it won't be scheduled until 8 cores are available, and in some situations it will sit on 8 cores during its duration whether it is only using 1 or all. If you have a large number of smaller VMs, scheduling can greatly improves.
This isn't true for all hypervisors and situations. You mileage may vary.
http://techreport.com/review/26058/the-ssd-endurance-experim...
Not to slam what Linode is doing here, and I'm sure there are probably lots of great reasons to buy datacentre-grade SSDs, but just thought I'd point out that slowing down over time (or data integrity issues) are not really consumer-grade problems any more :-)
I know it would read files faster, but in most cases reading a couple of PHP files is not such a big improvement.
My guess would be maybe databases ? Read time improvement for MySQL ?
dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
Linode: 1073741824 bytes (1.1 GB) copied, 1.09063 s, 985 MB/s D.O: 1073741824 bytes (1.1 GB) copied, 3.23998 s, 331 MB/s
dd if=/dev/zero of=test bs=512 count=1500 oflag=dsync
Linode: 768000 bytes (768 kB) copied, 0.478633 s, 1.6 MB/s D.O: 768000 bytes (768 kB) copied, 1.01716 s, 755 kB/s
Our Linode server (16 GB plan) has been performing terrible lately wrt I/O (compared to, say, a Macbook Pro running the same computations), and we decided we've had enough. I guess we'll have to compare the two after the upgrade and decide.
Compare the look and feel of https://www.linode.com/pricing/ and https://www.digitalocean.com/pricing/
It also does a fair bit more so apples to oranges a little bit.
However, I am seriously considering a move to Amazon Web services for one main reason: I need to decouple the hard drive space from the ram. The hard drive space is so expensive on linodes!!
I think their platform needs some love, it is a bit clunky to work with sometimes. But they are my favorite host.
I'm embarrassed to say that once upon a time I used library.linode.com to help walk me through my first Linux server setup... running on Digital Ocean. Yes, I felt like a complete douchebag. I wanted to use Linode but I was one of those $5/month people.
However it left me with a sense of obligation to give Linode business someday when I could justify/afford doing so. It looks like Linode just gave me the opportunity to do that.
It's cool of Linode to make the library available to everyone, not just customers.
Shame browsing it since the redesign is a complete clusterfuck between articles and community forum posts!
But that is funny, they copied so many aspects of Digital Ocean's design.
- 2007: http://web.archive.org/web/20071214070928/http://www.linode....
- 2013: http://web.archive.org/web/20131228003146/https://www.linode...
- 2014: https://www.linode.com/
Give me my beveled borders back!
I know that's not a big price difference, but some website really don't need a lot of resources. they work well on D.O's 5$ server, and I have really a lot of them.
Should I upgrade? Do I want 2 x RAM for 1/2 vCPUs? =)
Transfer - How much they let through the pipe.
Just a guess.
> What happens if I exceed my monthly transfer quota?
> You will be invoiced $0.10 for each GB over your pooled network transfer quota. Please note that all inbound traffic is free and will not count against your quota.
Bandwidth is the maximum Mbps that your VPS can spill out at any moment, whereas transfer is the maximum amount of per-month cumulative traffic that you can send out before incurring on additional traffic costs.
Its like downloading a 1 GB file to your computer using a 56k modem or a cable modem... the transfer amount will be 1 GB either way, but the cable modem will be a hell of a lot faster due to the increase in its bandwidth. As you upgrade your plan with Linode, your "modem" gets faster, however DO doesn't mention the speed of their "modem" or if its speed is affected by the price level you select.
bandwidth = d(transfer) / dt
edit: I just finished the migration, my disk speed test is through the roof, free ram is phenomenal!
For VMs that are not hypervisor-aware, the hypervisor must have all of that VM's vCPUs available at execution time since it cannot always anticipate which vCPUs the guest OS will execute against.
With fewer vCPUs, one might see what you're alluding to; better utilization and lower wait states because it's easier to schedule 2 CPUs consistantly than 8 CPUs on a host running multiple VMs.
Of course, that's in a VMware environment, so forgive me if Linode's hypervisor of choice avoids this problem I'm sure they're using KVM or Xen or something along those lines, maybe they're not as susceptible.
Long version: "If you take the upgrade, you inherit the new plan specs, vcpus and all.
We’ve greatly reduced the contention on these new machines compared to our old structure, and in testing this new arrangement provides much more consistent CPU time with less potential for steal. We think it’s great and totally worth the move, otherwise we wouldn’t have done it. These machines are incredibly fast, faster procs, SSDs, the network is incredible, etc."
From Caker's comment on the blog. It seems that this was done to reduce fighting over core and provided more consistent fair availability of processing power when they tested it b/t VMs.
If your hosts have, say, dual 4-way CPUs, and you're giving your VMs 8 vCPUs, then a single VM can execute per clock cycle since a VM needs all of it's vCPUs made available to the guest OS. With 8 VMs, that means one VM is executing every 8th clock cycle.
If you "downgrade" those VMs to 2 vCPUs, then 4 VMs can execute per clock cycle, and that VM can now execute every other clock cycle instead of waiting 8 cycles. More work gets done, even though the amount of CPUs has gone down.
Since most VMs are probably executing work that only has 1-2 threads, then there's no loss from lack of parallelism. Remember, a VM needs all cores available, regardless of how many threads need to be executed.
Of course, some workloads do need that many threads, and so balancing number of cores vs. available execution time becomes a little more tricky. but based on what you shared, it sounds like Linode took a closer look and came to the same conclusion.
This seems wrong to me. We're talking about virtualization; technologically, it is absolutely feasibly to have only one physical CPU running a VM even if the VM sees multiple virtual CPUs. And it seems like having this capability in virtualization software from the very beginning is really a no-brainer.
Evidence for your claim, please ;-)
Gabe spells it out pretty well here: http://www.gabesvirtualworld.com/how-too-many-vcpus-can-nega...
In a previous environment of mine, we ran dual socket, 4-way CPUs. VMs were configured with a mix of 1, 2, and 4 vCPU VMs. Our VMs appeared slow, especially on our 4-way systems. However, CPU utilization was low. More digging revealed that our co-stop values were high, meaning that the system couldn't schedule execution time effectively, meaning the VM had to sit in a READY state, which kept CPU utilization low.
Our first fix was to rebalance our cluster, so that 1 and 2 vCPU VMs were relegated to their own set of hosts, and our 4 vCPU VMs executed on their own set. Instantly, out co-stop values dropped, and CPU utilization rates went up...they were now doing work!
VMware briefly talks about the issue here: http://kb.vmware.com/selfservice/search.do?cmd=displayKC&doc...
If you'd really like the nuts and bolts of it, then those can be found here: https://www.vmware.com/files/pdf/techpaper/VMware-vSphere-CP...
The VMware co-scheduler has improved over the years, but I still read (The "Mastering vSphere 5.5" book by Scott Lowe carries a warning on this as well) that carefully balancing vCPUs is a must in a VMware environment. (Again, I don't believe Linode uses VMware, so I can't say with any certainty that KVM or Xen exhibit this behavior.)
So why can't we run 8 vCPUs on one physical one? Because while they're virtual to some extent, they're not completely abstracted. Anytime the hypervisor has to perform a translation between the guest OS and the host, a performance penalty is incured. So while the hypervisor may abstract scheduling, it reveals as much of the physical CPU to the guest VM as possible. Here's a little blurb from an older VMware manual explaining a bit of the difference: http://pubs.vmware.com/vsphere-4-esx-vcenter/index.jsp?topic...
CPU virtualization =/= emulation
For this reason, (again, at least in a VMware environment) we can't give a VM more vCPUs than exist pCPUs to align them to.
Hope this helps!
In the past on certain host servers you get a great experience - low latency and the ability to burst CPU usage. However occasionally you get provisioned on an awful server where the latency of your server varies significantly, and your apps struggle to get a decent share of the CPU.
I'd rather see my servers have a small but more fair amount of burst instead of all packages getting 8 CPUs with some of them getting a bad experience from noisy neighbours.
As for backups, Linode backups seem to get a bad reputation. They do take a snapshot of a running instance - but reports from the forums indicate that they regularly fail, leaving you with a missing backup at some points. The only way of restoring a backup is to deploy that backup as a new server.
I'd recommend avoiding Linode backups and doing your own.
I agree it would be nice to do upgrades in place but presumably they have very good reasons for not doing so. Are you aware of any provider which does this in a seamless way? I'm not really sure how they'd do it, particularly for RAM.
Not true. You can restore a backup to a node as long as it has enough unallocated disk space. The simplest ways to create enough unallocated disk space are to create a new node or to delete or resize all your disk images.
$ dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync
1024+0 records in
1024+0 records out
1073741824 bytes (1.1 GB) copied, 35.8268 s, 30.0 MB/s
Note that on AWS your hard drive isn't on the machine running your VM. If you want to test local disk speed, do it in /mnt, where local disk storage is mounted... but remember that data stored there won't persist if you turn your instance off.
- DO has excellent and easy to understand API - Step by step guides on setting up and running anything - Minimal and simple
To entice me, it's no longer just a matter of price, DO has extra value added, largely due to their simplicity.
now I definitely don't think there's much linode can do further to entice me unless they matched digital ocean's pricing lower than 0.03/hr
I just want to install some personal projects there for which even SSD's are overkill...