ASP.Net 服务器数量估计
假设我们的平均页面权重为 P KB，并且每单位时间（比如说每小时）有 N 次访问。 我们如何估计在合理的响应时间下支持此负载所需的服务器数量？
Let's assume our average page weights P KBytes and we've got N visits per unit time (let's say, per hour). How could we estimate the number of servers needed to support this load with a reasonable response time?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
影响服务器性能的因素有很多（CPU、RAM、I/O、缓存、本地或外部数据库、网络等），您甚至无法猜测给定项目所需的服务器数量。
我发现任何试图弄清楚这一点的人都走上了错误的道路，因为他们经常有一些不切实际的想法，认为他们将使网站变得非常受欢迎。
我的建议是，只需构建您的应用程序并使用 1 个服务器，假设您可能需要一个服务器场，因此根据此构建您的软件（这在 .NET 中几乎意味着您不需要做任何不同的事情）。 只有当你有实际需要时才购买更多服务器，预期购买/租用服务器总是会导致金钱浪费，你不是亚马逊也不是谷歌，除非你有当前的数据，否则你无法准确地假设未来的扩张。
我想您会发现一台好的服务器速度快得惊人，并且可以处理大量用户。 请记住 StackOverflow（我上次看到的）仅在 2 台服务器上运行； 一个网络服务器和一个数据库服务器......就是这样。
There are so many factors to server performance (CPU, RAM, I/O, cache, local or external database, networking, etc) that you can't even guesstimate the amount of servers needed for a given project.
I find anybody who tries to figure this out is going down tho wrong path, because they often have some unrealistic idea that the site they are going to make it going to be insanely popular.
My advice, just build your app and use 1 server, assume you might need a server farm, so build your software according (which in .NET pretty much means you don't do anything different). Only buy more servers when you have an actual need, buying/renting servers in anticipation will always lead to wasted money, you're not Amazon nor Google, you can't accurately assume future expansion until you have current figures.
I think you'll find 1 good server is surprisingly fast and can handle a lot of users. Keep in mind StackOverflow (last I saw) only runs on 2 servers; a web server and a database server... that's it.