5 ms·
If we want securely-isolated low-horsepower machines, why don't we just fill server-racks with large numbers of low-horsepower physical computers, rather than s
by MaxBarraclough 7y ago
If we want securely-isolated low-horsepower machines, why don't we just fill server-racks with large numbers of low-horsepower physical computers, rather than small numbers of big-iron computers using software isolation in the form of VMs?
Wouldn't that win half the battle, at least on server-side? It wouldn't apply to workstations, of course. Malicious/untrusted processes running there would still need to be isolated (malicious JavaScript in the browser, say).
Also, am I missing something, or are these concerns really not applicable to gaming applications (which the article emphasises)? That's a highly trusted codebase, so securely containing it isn't worth a 15% performance hit, no?
- nexuist 7y agoThe cloud is only able to be cost effective because they are able to utilize those fleets of big-iron computers to provide nearly infinite VMs and resources to anyone who signs up for their services. Relegating each customer to their own physical computer would raise costs so high as to essentially eliminate the purpose of the cloud's existence, and most businesses would be better off going back to their own data centers at that point.
- sigstoat 7y ago> Relegating each customer to their own physical computer would raise costs so high as to essentially eliminate the purpose of the cloud's existence plenty of places rent bare metal machines, and the price doesn't seem quite that world-ending. see packet.net for instance. and it only gets better if on the bare metal machine you get to turn off all of the performance-draining fixes.
- angry_octet 7y agoIt's actually much cheaper than cloud. It doesn't have the scaling flexibility, but that is partially compensated for by running faster, lower latency, etc. Lots of people use Cloudfront etc but still host on their own bare metal.
- MaxBarraclough 7y agoIsn't it still 'cloud'? It's still on a server somewhere that I don't think about, which is really all 'cloud' tends to mean. I don't care whether Amazon use virtualisation to get me my 'instance'. They're always careful to stick with 'instance', and never to commit to 'VM'. Wise move, now that they're offering physical ('dedicated') instances [0]. Time will tell whether they take an interest in low-horsepower dedicated instances. [0] https://aws.amazon.com/ec2/pricing/dedicated-instances/ https://aws.amazon.com/ec2/pricing/dedicated-instances/
- angry_octet 7y agoThere is a non-smooth transition from a server you own/lease and sits in specific rack in a known data centre with well understood routing and one provisioned as a dedicated instance in AWS/Azure etc that you manage with an API.
- MaxBarraclough 7y ago> Relegating each customer to their own physical computer would raise costs I'm not convinced the cost difference would be a showstopper. More little computers rather than few big computers. Same total horsepower. More motherboards, sure.
- gmueckl 7y agoMore boards, more rack space, more hardware management overhead, more and longer wiring with associated losses from resistance, bigger buildings... it's not really simple.
- MaxBarraclough 7y ago> More boards, more rack space Not if they can be made smaller and packed more densely. > more hardware management overhead I'm not sure this is a significant issue. > more and longer wiring I don't think this follows. They could be clustered. A cluster could be made to look a lot like a conventional big-iron server. We're talking about replacing a single large machine running, say, 16 VMs (each with an IP), with 16 small machines (each with an IP). Put an Ethernet switch at the last-mile and it's virtually the same, no? Different number of MAC addresses, sure.
- rubber_duck 7y agoFor certain kind of workloads renting bare metal is waay cheaper than VMs. What the small time bare metal providers cant compete with is all the different services sold along with the VMs. If it was just price per VM I suspect bare metal renting would be a lot more cost efficient in a lot of scenarios.
- dfrage 7y agoThe other area they can't complete is on variable or disaster recovery scenarios, the sort where you'll reserve CPU instances, but only spin them up for your heavy load parts of the day or when you have an unexpected migration. And when you're not using them, AWS puts them on their spot market. They're probably a bad match for when you have a single batch of work to do, like when the New York Times converted their archives, or every time Netflix has to reencode their video library.
- elorant 7y agoMore machines means more power to cool them. Electricity bills are a big chunk of the cost of running a datacenter.
- dfrage 7y agoI was just discussing this with a friend. Obviously there's a certain degree of multi-tenancy sharing that's most cost effective. For electrical power use and removing heat there's a floor where, if not being used, the best you could do would be to turn a system off, which has its own issues. Go too far and you won't be able to also run a spot market in CPU instances like AWS does.
- MaxBarraclough 7y ago> For electrical power use and removing heat there's a floor where, if not being used, the best you could do would be to turn a system off, which has its own issues. What issues? If your cloud architecture can't save power when demand is low, how can that be a positive? > Go too far and you won't be able to also run a spot market in CPU instances like AWS does. As I understand it, a spot market isn't ever an architectural goal, it's a way to exploit the practical realities of unused resources/capacity. If that necessity goes away, that'd be a win. I see at least 3 possibilities: 1. The spot market is about filling temporarily-vacant VM slots on host physical machines 2. Additional physical machines must be kept online so that VMs can be quickly spun-up, and the spot market is about capitalising on this necessity (this is really a variation on Option 1) 3. The spot market is about deriving at least some revenue from the unutilised fraction of an always-on fleet, encouraging customers to run heavy jobs during times of low load on your cloud I doubt Amazon's fleet is always-on -- I imagine they have fairly significant capacity in reserve to keep up with growth and spikes -- so I doubt it's Option 3. (This is a perfectly obvious question but I really can't find a definitive answer. Maybe my Google-fu is weak today.)
- luhn 7y agoI think Amazon’s hands are mostly tied when it comes to powering off machines. Many VMs are run indefinitely, so whatever machine they’re on has to stay powered on. They may have live migrate (I think they do, but no official word), but they can’t be too aggressive about that or customers will notice.