确定网站容量
我的一个客户有一个网站，他们需要确定该网站当前的“可扩展性”程度。我的意思是同时浏览该网站的用户数量。
这是一个 .net 中的自定义电子商务应用程序，不是我自己编写的，代码是……好吧，只是说，有点可疑。
一家更大的公司正在寻求收购它们/投入资金，但他们需要某种形式的指标来显示在其崩溃之前可以承受多少负载。这家大公司有能力向庞大的用户群“打开水龙头”——如果网站因流量的一个喷嚏而崩溃，那么显然他们不想这样做。
这里提供什么好的指标？我怎样才能获得它？
编辑：问题已修改
A client of mine has a website and they need to determine how 'scalable' the site currently is. What I mean by this is the number of users browsing around the site concurrently.
It's a custom e-commerce app in .net, not written by myself and the code is... well lets just say, a bit dubious.
A much bigger company is looking to buy them / throw funding their way but they need some form of metrics to show how much load it can take before it falls apart. This big company has the ability to 'turn on the taps' to a huge user base - and obviously doesn't want to do that if the site is going to fall over with a sneeze of traffic.
What is a good metric to provide here? And how can I obtain it?
Edit: Question revised
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我总是使用 Apache 的“ab”工具： 链接文本
从以下位置运行它不同的机器，最好是没有防火墙规则的 BSD 或 Linux 机器，因为防火墙规则会限制工具的性能。因为否则结果可能不那么可靠。如果您使用 Windows 计算机，请确保您使用的计算机不限制活动 TCP 连接数。
当使用“ab”时，您要查找的数字是“每秒请求数”。尝试使用并发开关，看看在出现大量错误之前或每秒请求数快速下降时可以处理多少并发用户。
当您注意到网络服务器出现严重问题时，您应该重新启动网络服务器，并让它休息一段时间，然后再继续测试。
I always use Apache's "ab" tool: link text
Run it from a different machine, preferably a BSD or Linux machine with no firewall rules that will limit the performance of the tool. Because otherwise the result might not be as reliable. If you use a Windows machine, make sure you're using one that isn't limiting the number of active TCP connections.
When using "ab", the number you're looking for it "Requests per second". Experiment with the concurrency switch to see how many concurrent users you can handle before you're getting a lot of errors, or when the requests per seconds is dropping rapidly.
When you are noticing the webserver is having serious issues you should restart the webserver, and let it rest for a while before continuing the test.
您最好进行托管负载测试，因为这可能会让您更深入地了解现实场景（例如 http://www.scl.com/software-quality/hosted-load-test，但没有使用它们的经验）。
此外：据我所知，可扩展性并不是可以为多少并发用户提供服务，而是当网站变大时提供更多服务的难易程度（通过添加额外的服务器等，网站扩展的难易程度） up，代码库是否允许使用无限数量的服务器等）
You'd be better off with a hosted load test, as this might give you more insight on realworld scenario's (something like http://www.scl.com/software-quality/hosted-load-test, no experience with them though).
Furthermore: scalability is as far as I know, not how many concurrent users can be served, but the way how easy it is to serve more when the site grows bigger (by adding extra servers etc, how easy is it for the website to scale up, does the codebase allow to use unlimited number of servers, etc.)
嗯，我想这取决于客户关心什么。
他们关心有多少用户可以同时访问该网站吗？报告这一点，但从另一台服务器同时运行请求直到它死掉，然后获取数字。
他们还关心其他事情吗？
对我来说，当有人说他们希望它能够“扩展”时，这实际上意味着他们不知道自己想要什么。因此，尝试与他们交谈，并获取他们想要看到“扩展”的具体细节，然后，一旦找到要分析的领域，您就可以轻松地进行分析，并尝试改进它们。
Well, I suppose it'll depend on what the client cares about.
Do they care about how many users to can access the site at once? Report on that, but running simultaneous requests from another server until it dies, then get the number.
Do they care about something else?
For me, when someone says they want it to 'scale', it really means they have no idea what they want. So try and talk to them, and get specific details of what, exactly, they want to see 'scaling', and then, once you find the areas to analyse, you can do so trivially, and attempt to improve them.