In nearly every server application, the question of thread pools and work queues comes up.
几乎在每个服务器应用程序中都会出现线程池和工作队列问题。
To achieve a high transaction throughput rate, it may be necessary to consider the distribution of work between queues, queue managers, and application server instances.
要获得高的事务吞吐量率，可能需要考虑在队列、队列管理器和应用程序服务器实例之间分配工作。
Client response times are not always an indicator that the server is near saturation, because work is buffered in the server queues.
客户端响应时间并不总能反映服务器已接近饱和，因为负载在服务器队列中得到缓冲。
Buildd.rex: This script runs on each guest operating system and accesses the queues on the Web server looking for work.
rex：该脚本运行在每个客户操作系统上并访问Web服务器上的队列来查找工作。
Let's assume your WebSphere Application Server is maintaining the maximum number of servant regions, all bound to different service class work queues.
假设您的WebSphereApplicationServer正在保持最大服务区域数量，这些服务区域全都绑定到不同的服务分类工作队列。
Buildserver.rex: This script runs on the Web server and maintains the queues that the guest operating systems use to look for work.
rex：该脚本运行在Web服务器上并维护客户操作系统用于查找工作的队列。
WebSphere Application Server is designed to process a large number of parallel short-time tasks, and work queues and thread pools are two components that are used often to handle parallel workload.
WebSphereApplicationServer旨在处理大量的并行短时间任务，工作队列和线程池是两个经常用来处理并行工作负载的组件。
WebSphere Application Server deployment is a series of queues, and it's best to only allow the amount of work into a queue for which capacity exists to perform work.
WebSphere应用服务器部署是一系列队列，最好只允许能力范围内的工作量进入队列。
WebSphere Application Server deployment is a series of queues, and it's best to only allow the amount of work into a queue for which capacity exists to perform work.
WebSphere应用服务器部署是一系列队列，最好只允许能力范围内的工作量进入队列。
应用推荐