asp.net 网站加载估计指南？
我想知道系统管理员是否有什么好的指南来计算托管 ASP.NET 网站所需的资源？ 我想对所需的处理能力进行一些估计，以便知道我需要获得哪种 VPS/云。
I wonder if there is any good guideline for system administrators to calculate the resources needed to host an ASP.NET website? I want to do some estimates on the processing power needed so I know what kind of VPS/Cloud I need to get.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
负载测试将是您最好的解决方案。
应用程序的扩展方式有所不同，具体取决于大量变量，包括问题解决类型、解决方法和其他因素。
100 个并发用户消耗 10% CPU 并不意味着 500 个并发用户消耗 50%，它可能是 20%，也可能是 100%。
您的瓶颈可能是处理器、内存或网络带宽。
如果没有实际将负载施加到您的应用程序上，任何估计都将仅仅是猜测，并且很可能被证明是错误的。
Load testing will be your best solution.
Applications differ in how they scale depending on a large number of variables including types of problem solving, approach to solution and other factors.
100 concurrent users consuming 10% CPU does not mean 500 concurrent at 50%, it could be 20% or it could be 100%.
Your bottleneck could be processor or memory or network bandwidth.
Without actually placing the load on your application, any estimation will be merely a guess and will quite likely be proven incorrect.
完全取决于应用程序。
如果您查看特定应用程序的要求，则将其放在您拥有的任何看起来像服务器的硬件上，启动 perfmon 并选择良好的计数器和计数器来运行。 然后运行一些自动化工具进行负载测试，针对应用程序执行一些常见任务。 看看它的性能如何，然后根据您拥有的硬件、您运行的负载和性能进行猜测。 效果如何。
根据经验，我发现 ASP.NET 应用程序在 Web 服务器端出现的瓶颈通常是 RAM。
您需要担心的是运行 ASP.NET 应用程序后端的数据库:-) 我想说，有 9/10 次我看到 ASP.NET 应用程序出现性能问题，数据库一直是瓶颈。
Totally depends on the application.
If your looking at requirements for a specific application, then put it on whatever hardware you have that looks like a server, start perfmon running with a good selection of counters & then run some automated tools for load testing, performing some common tasks against the application. See how it performs, then take a guesstimate based on the hardware you have, the load you ran against it & how it measured up .
From experience the bottlenecks i see appearing with ASP.NET apps at the webserver end is usually RAM.
It's the database that runs the back-end of the ASP.NET application you need to worry about :-) I'd say 9/10 times I've seen performance issues with ASP.NET apps, the DB has been the bottleneck.