IIS 6.0 的限制是什么
IIS 6.0 的限制是什么？例如，如果我需要在 IIS 6.0 上托管 100,000 或 200,000 个网站，我需要多少台机器？或者出于某种原因，在这种情况下 IIS7 是否是更好的选择？
What is the limit of IIS 6.0? like for example if i need to host 100,000 or 200,000 websites on IIS 6.0, how many machines would i need? or is IIS7 would be a better choice in this case for some reason?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
使用 IIS 托管如此多的网站将导致许可费用过高。大多数大型 Web 托管都是使用 Apache 在 Linux 上完成的。
Hosting that many websites with IIS will be cost-prohibitive in licensing fees. Most large scale web hosting is done on Linux using Apache.
正如上面的评论中提到的，规模并不是您在 IIS 中创建的网站数量，而是这些网站的复杂程度和繁忙程度。
在IIS6中，一个网站并不一定等同于服务器上的一个正在执行的进程。应用程序池可以将多个网站分组为单个执行进程，以分组和/或隔离应用程序。或者，单个应用程序池可以生成多个执行进程，以更好地利用服务器硬件。
如果您在问题中提供有关您到底想要实现什么目标的更多详细信息，可能会有所帮助。如果您要为数十万个站点提供服务，那么与托管公司合作可能是个好主意，或者从了解 IIS 详细信息或其他平台并具有可操作性的人员那里获得帮助具有处理大型托管场景的经验。
As mentioned in the comments above the scale isn't so much the number of websites you create in IIS, but how complex and how busy those sites are.
In IIS6 one website does not necessarily equate to one executing process on the server. Application pools can group multiple websites into a single executing process to group and/or isolate applications. Alternately a single app pool can spawn multiple executing processes to make better use of server hardware.
It might help if you were to provide more detail in your question about what exactly you're trying to accomplish. If you're going to be serving hundreds of thousands of sites it would probably be a good idea to partner with a hosting company, or get some assistance from someone who knows the ins and outs of IIS, or another platform in detail and has operational experience with working through large-scale hosting scenarios.
在任何与性能相关的方面，IIS7 与 IIS6 并没有根本不同；但有一个例外：您可以在“本机”管道模式下运行 ASP.NET，从而绕过某些处理步骤。我更喜欢 IIS7（如果可以选择的话），因为它的可管理性优势。但就像这里其他人所说的那样：如果没有更多信息，这个问题就无法回答。
IIS7 is not radically different from IIS6 in any performance-related way; with one exception: you can run ASP.NET in a "native" pipeline mode that bypasses some processing steps. I prefer IIS7 (if I can choose) because of its manageability advantages. But like everyone else said here: the question is impossible to answer without more information.