问题描述
我工作的一个客户的建议，他们将需要升级他们的网络基础设施，以支持托管ASP.NET应用程序。从本质上讲，我需要估计峰值使用一个系统与用户的已知量（目前250）。像一个简单的回答你需要一个专用的T1线路很可能足够了，但我想有数据备份。
I am working on a client proposal and they will need to upgrade their network infrastructure to support hosting an ASP.NET application. Essentially, I need to estimate peak usage for a system with a known quantity of users (currently 250). A simple answer like "you'll need a dedicated T1 line" would probably suffice, but I'd like to have data to back it up.
Another问题引用NetLimiter，它看起来pretty光滑获取的是正在使用的感觉。
Another question referenced NetLimiter, which looks pretty slick for getting a sense of what's being used.
我的总体思路是，我会解雇Web应用程序和使用该系统像我预计它会在用户使用时，确实在一个悠闲，超过一定的时间跨度，然后乘以带宽使用率用户和除以时间的数量。
My general thought is that I'll fire the web app up and use the system like I would anticipate it be used at the customer, really at a leisurely pace, over a certain time span, and then multiply the bandwidth usage by the number of users and divide by the time.
这似乎并不十分科学。这可能是一个提案不够好，但我想看看有没有更好的办法。
This doesn't seem very scientific. It may be good enough for a proposal, but I'd like to see if there's a better way.
我知道有可用于测试Web应用程序的性能负载的工具，但它似乎是这些不准确的模拟带宽测试目的峰值用户负载（太多了一次）。
I know there are load tools available for testing web application performance, but it seems like these would not accurately simulate peak user load for bandwidth testing purposes (too much at once).
该平台为Windows / ASP.NET和应用程序在SharePoint（MOSS 2007）主办。
The platform is Windows/ASP.NET and the application is hosted within SharePoint (MOSS 2007).
推荐答案
在代替带宽使用一个很好的报告工具，你总是可以做一个粗略的猜测。
In lieu of a good reporting tool for bandwidth usage, you can always do a rough guesstimate.
N =的页面访问量在最繁忙的时间数
P =平均页面大小
N = Number of page views in busiest hourP = Average Page size
（N * P）/ 3600）=每秒平均流量。
(N * P) /3600) = Average traffic per second.
服务器本身也会有很多关于可能DB服务器/ NAS /等更多的内部交通。但是，面向外，应该给你上利用一个非常粗略的想法。显然，你将需要远远超过上述数值，你永远要利用100％，并允许其他通信。
The server itself will have a lot more internal traffic for probably db server/NAS/etc. But outward facing that should give you a very rough idea on utilization. Obviously you will need to far surpass the above value as you never want to be 100% utilized, and to allow for other traffic.
我也不会建议使用类似250的用户任意数量。使用的最重的生产日期/小时作为参考。双倍和三倍，如果你喜欢，但是这会给你的用户行为预期的分布，如果你有很好的日志文件/用户审核。这将有助于使你的猜测更准确。
I would also not suggest using an arbitrary number like 250 users. Use the heaviest production day/hour as a reference. Double and triple if you like, but that will give you the expected distribution of user behavior if you have good log files/user auditing. It will help make your guesstimate more accurate.
另一个评论者指出，数据中心是一个好主意，当冗余和带宽可用性成为是一个问题。您的需求可能会有所不同，但不要轻易解雇的建议。
As another commenter pointed out, a data center is a good idea, when redundancy and bandwidth availability become are a concern. Your needs may vary, but do not dismiss the suggestion lightly.
这篇关于什么是估计为Web应用程序的峰值带宽需求的最准确的方法是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！