梁斌penny_Penny Pinching在云端：您的Web应用程序不需要64位

最新推荐文章于 2024-08-11 20:00:32 发布

cunfusq0176

最新推荐文章于 2024-08-11 20:00:32 发布

阅读量258

点赞数

文章标签： java jvm linux 编程语言 docker

原文链接：https://www.hanselman.com/blog/penny-pinching-in-the-cloud-your-web-app-doesnt-need-64bit

版权

梁斌penny

Often times I hear folks say that they need (or want) 64-bit support when they deploy to the cloud. They'll deploy their modest application to Azure, for example, as a Web Application, then immediately go to the settings and set it to 64-bit. So many years later and it's "do I need 64-bit" is still confusing to a lot of people.

我经常听到人们说他们在部署到云时需要(或想要)64位支持。他们会将其适度的应用程序作为Web应用程序部署到Azure，例如，然后立即转到设置并将其设置为64位。这么多年以后，“我需要64位”仍然让很多人感到困惑。

I made basic Hello World ASP.NET app and deployed it. Now, I go to that Web Apps "blade" in the Azure Portal, click Tools, then Process Explorer (after exercising the app a little.) I'm running 32-bit here. The K is the Kudu "sidecar" deployment site (for things like Git deploy and diagnostics), and the other icon is the production site.

我制作了基本的Hello World ASP.NET应用程序并进行了部署。现在，我转到Azure门户中的“ Web应用程序”，单击“工具”，然后单击“进程资源管理器”(稍作练习后。)我在这里运行32位。 K是Kudu的“ sidecar”部署站点(用于Git部署和诊断之类的东西)，另一个图标是生产站点。

30 meg working set for IIS in 32 bit mode

Now, I'll swap it to 64-bit and exercise the web app again. Remember, this app is just a super basic app.

现在，我将其交换为64位并再次使用该Web应用程序。记住，这个程序只是一个超级基本的应用程序。

102 meg working set in IIS in 64-bit mode

See how the working set (memory) jump? It's a little extreme in a hello world example, but it's always going to be bigger than 32-bit. Always. 64-bit'll do that. Does your site need to address more than 4 gigabytes of memory from any single process? No? Then your web app probably doesn't need to be 64-bit. Don't believe me? Test it for yourself.

看看工作集(内存)如何跳跃？在hello world示例中，这有点极端，但它总是大于32位。总是。 64位会做到这一点。您的站点是否需要通过任何单个进程处理4 GB以上的内存？没有？然后，您的Web应用程序可能不需要是64位的。不相信我吗自己测试一下。

I'll go even further. Most web apps don't need 64-bit, but here's the real reason. If you stay 32-bit when putting your Web Application in the cloud you can fit more applications into a limited space. Maybe your Medium App Service Plan can actually be a Small and save you money.

我会走得更远。大多数网络应用程序不需要64位，但这是真正的原因。如果将Web应用程序放在云中时保持32位，则可以在有限的空间内容纳更多的应用程序。也许您的“中型应用服务计划”实际上可以算是小型计划，并且可以为您省钱。

Until 64-bit only is the default in things like Nano Server, today you can fit more Web Apps into limited memory if you stick with 32-bit.

在直到Nano Server之类的默认设置中，只有64位才是默认设置，今天，如果您坚持使用32位，则可以在有限的内存中容纳更多的Web应用程序。

I personally have 18 web apps in a Standard Small App Service in my personal Microsoft Azure account. They are sites like my podcast Hanselminutes and they get decent traffic. But most never get over 300-600 megs of memory and there's literally no reason for them to be 64-bit today. As such, I can fit more in the Small App Service Plan I've chosen.

我个人的Microsoft Azure帐户中的Standard Small App Service中个人有18个Web应用程序。它们像我的播客Hanselminutes一样，获得了可观的访问量。但是大多数都不会获得超过300-600兆的内存，而实际上没有理由让它们成为64位。因此，我可以更适合选择的“小应用程序服务计划”。

18 web apps in a single app service plan

Remember that the Azure Pricing Calculator isn't totally obvious when it comes to Web Applications. It's not ~$55 per Basic Web Site. There's a Virtual Machine under there, they call the whole thing an "App Service Plan" and your Web Apps sit on top of that plan/VM. It's really $55 for a plan that supports as many web applications you can comfortably fit in there.

请记住，就Web应用程序而言，Azure定价计算器并不十分明显。这不是每个基本网站约55美元。下面有一个虚拟机，他们称整个事情为“应用程序服务计划”，而您的Web应用程序位于该计划/ VM之上。对于支持尽可能多的Web应用程序的计划来说，实际上是55美元。

The cloud is a great deal when you're smart about the resources you've been given. If you're using Azure and you're not using most of the the resources in your service plan, you're possibly wasting money.

如果您对所获得的资源非常了解，那么云计算就非常重要。如果您使用的是Azure，但没有使用服务计划中的大多数资源，则可能会浪费金钱。

What Penny Pinching in the Cloud tips do you have? Disagree with this advice? Sound off in the comments.

您在云端获得Penny Pinching的哪些技巧？不同意这个建议？在评论中听起来不错。

梁斌penny_Penny Pinching在云端：您的Web应用程序不需要64位

相关链接 (Related Links)