TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Surprising Scalability of Multitenancy

75 点作者 federicoponzi大约 2 年前

5 条评论

Animats大约 2 年前
I'd seen a more useful paper on this subject, on how to organize your game servers for a big MMO. The most economical strategy was to own your servers for the base load, and go out for AWS for peaks. Running 24/7 compute bound work on AWS is at least 2x as expensive as owning your own co-located servers.
评论 #35285253 未加载
评论 #35284598 未加载
评论 #35286784 未加载
revelio大约 2 年前
The author sounds a bit scared. Maybe the recent wave of &quot;we can save $$$ by leaving AWS&quot; articles have them rattled?<p>Yes, multi-tenancy and improved hw utilization can save money ... <i>for Amazon</i>. That&#x27;s of no use if they lack sufficient competition and just capture the savings as profits. Then you&#x27;re just wasting time on debugging weird contention issues and cloud cost optimization consultants so Bezos can get richer.<p>The profit margins on AWS are so huge that even though you they can binpack better it often doesn&#x27;t matter, you&#x27;re going to still save money by going to either a cheaper cloud or using your own HW (or renting your own dedicated HW). The savings from multi-tenancy are drowned by the added costs.<p>One intriguing model that might be worth exploring is micro-clouds. In that model there&#x27;s a kind of clearing market, and users with strong diurnal cycles and not many batch jobs can re-sell their CPU capacity at night to other users. They just implement some Lambda-ish API and configure the kernels&#x2F;hypervisors to always prioritize their own jobs over guests. The guests don&#x27;t care because they&#x27;re getting the resources cheap, for the company the additional income offsets the cost of their own machines and the market takes a cut. The difference vs today&#x27;s cloud models is it&#x27;s more decentralized and the &quot;cloud provider&quot; is really just a match maker, so it&#x27;s easy to set up competitors and margins would be low.
评论 #35288412 未加载
ec109685大约 2 年前
It’s ironic that AWS touts the benefit Lambda gets from overcommit, but if you build a lambda that simply turns around and makes an api call, you are paying full price for the cpu usage, even though it’s idle.
评论 #35285384 未加载
throwawaylinux大约 2 年前
Who is this surprising to? Timesharing, timeslicing, multiprocess, multitenancy,-- whatever you call the same underlying concept -- was one of the pivotal advances in computer systems. Surely no serious person is surprised it is effective.
评论 #35284619 未加载
评论 #35284468 未加载
评论 #35289152 未加载
RcouF1uZ4gsC大约 2 年前
One thing this scalability bets on is that side channel attacks won’t get better.<p>Spectre and related attacks already reduced CPU performance.<p>Shared hardware opens up the door for side channel attacks and hardening against those attacks is going to decrease performance.
评论 #35284642 未加载