ColdFusion 模板请求计数优化
在 ColdFusion 中，在管理员的“请求调整”下，如何确定同时模板请求的最大数量的最佳数量（或至少是一个好的猜测）？
环境：
CF8标准
IIS 6
Win2k3
SQL2k5 在一个单独的盒子上
In ColdFusion, under Request Tuning in the administrator, how do I determine what is an optimal number (or at least a good guess) for the Maximum Number of Simultaneous Template Requests?
Environment:
CF8 Standard
IIS 6
Win2k3
SQL2k5 on a separate box
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我想说每个核心至少 8 个，而不是每个 CPU。 我认为 8 个对于现代 CPU 核心来说有点低，我想说至少 12 个。
I would say at least 8 per core, not per CPU. And I think 8 is a little low given modern CPU cores, I would say at least 12.
找到正确数量的请求的方法是负载测试。 也就是说，当您改变请求数时，测量负载下吞吐量的变化。 任何重大变化都需要重新测试。 但我怀疑大多数人都会对如此大量的工作犹豫不决。
我认为一个好的经验法则是每个 CPU（核心）有 8 个线程。
就效率而言，线程数越少（在一定程度上），CPU 处理请求时进行的交换就越少。 如果您的页面执行速度非常快，那么较少数量的请求是最佳的。
如果您有较长的运行请求，特别是如果您有正在等待第三方（例如数据库）的请求，那么增加工作线程的数量将提高您的吞吐量。 也就是说，如果您的 CPU 没有忙于处理事务，您就可以有更多的并发请求来处理手头的任务。
尽管有点过时，但 Grant Straker 的书中有关请求调整的许多原则 CF Performance & 故障排除 是值得的。
The way of finding the right number of requests is load testing. That is, measuring changes in throughput under load when you vary the request number. Any significant change would require retesting. But I suspect most folks are going to baulk at that amount of work.
I think a good rule of thumb is about 8 threads per CPU (core).
In terms of efficiency, the lower the thread count (up to a point) the less swapping will be going on as the CPU processes your requests. If your pages execute very quickly then a lower number of requests is optimal.
If you have longer running requests, and especially if you have requests that are waiting on third-parties (like a database) then increasing the number of working threads will improve your throughput. That is, if your CPU is not tied up processing stuff you can afford to have more simultaneous requests working on the tasks at hand.
Although its a little bit dated, many of the principles on request tuning in Grant Straker's book on CF Performance & Troubleshooting would be worthwhile.