The worker threads loop awaiting new requests.
工作线程循环等待新请求。
Create enough worker threads for best throughput.
创建足够的工作线程以实现最佳吞吐量。
This is where the worker threads are spawned, as in Listing 2.
这也是派生worker线程的地方，如清单2所示。
The number of worker threads is independent of the number of Web clients.
工作线程的数量与Web客户机的数量无关。
Queuing models can help identify the effects of blocking worker threads in an SOA.
队列模型能够帮助标识soa中阻塞工作线程的影响。
These queues are used to temporarily hold requests when worker threads aren't available.
这些队列用于在线程不可用时临时接收请求。
Adjust number of worker threads for each servant region by changing the workload profile.
通过更改工作负载概要调整每个服务区域的工作线程数量。
A variable number of worker threads are spawned to process (consume) requests off the queue.
为了处理(消费)队列中的请求，生成了不定数量的工作线程。
As the worker threads complete their transactions, the next work item in the queue is executed.
在工作线程完成其事务后，将会执行队列中的下一个工作项目。
Typically an application will also create a number of worker threads to process these notifications.
通常情况下，我们会在应用程序中创建一定数量的工作者线程来处理这些通知。
Blocked application server worker threads can negatively impact the server's capacity and throughput.
被阻塞的应用程序服务器工作线程可能会对服务器的容量和吞吐量造成负面影响。
Ultimately, two worker threads (one in server 1 and one in server 2) were blocked during this transaction.
最终两个工作线程(服务器1和服务器2上分别一个)在此事务期间都被阻塞。
PeriodicThread is the base class from which worker threads in the set of cooperating threads must be derived.
PeriodicThread是基类，从它派生出协作线程组中的worker线程。
As a result, Swing applications often require additional worker threads for long-running UI-related tasks.
因此，Swing应用程序经常需要额外的工作线程，用于运行时间很长的、同ui有关的任务。
The number of worker threads is three times your number of CPUs, but it's no less than 5 and no larger than 30.
工作线程的数量是CPU数量的三倍，但是不小于5和不大于30。
If you have long operations to perform, you should make sure to do them in extra threads (background or worker threads).
如果有耗时的操作，你应该把这些操作放在另外的线程中进行处理(后台线程或者工作线程)。
How do you choose the right workload profile and set the proper number of worker threads to achieve the best throughput?
如何选择正确的工作负载概要并设置恰当的工作线程数量才能实现最佳的吞吐量呢？
Keep in mind that Tomcat must allocate one thread per user, while the NIO server was configured with only four worker threads.
记住，Tomcat必须为每个用户分配一个线程，而NIO服务器只配置有4个工作线程。
If the reported value of active is continually reaching the value of total, then you should make more worker threads available.
如果所报告的active的值不断接近total的值，那么您需要让更多的worker线程可用。
A network router had issues and caused many worker threads within the WebSphere Application Server servant region to block.
某个网络路由器出现了问题，导致WebSphereApplicationServer服务区域的很多工作线程阻塞。
Tomcat was configured with a maximum thread count of 2000 while the example server was only allowed to run with four worker threads.
Tomcat是用最大的线程数量 2000来配置的，而示例服务器只允许用4 个工作线程运行。
Many worker threads can suddenly block and wait for some timeout to expire; in the meantime however, new work arrives to the server.
很多工作线程可能会突然阻塞，并等待超时过期，不过同时又有新工作送到服务器。
You only need to set a proper number of worker threads for workload execution, without having to consider the number of client requests.
您只需设置用于工作负载执行的适当工作线程数量，而不必考虑客户端请求的数量。
Because the TimerCallback function gets called on a worker thread, there are no skipped beats (assuming the availability of worker threads).
因为TimerCallback功能也是在工作者线程上被调用，没有一个跳动被跳过(假设有工作者线程可用)。
When the number of requests increases and the number of worker threads is too small, it may take a long time for requests to be processed.
当请求的数量增加，并且工作线程的数量太少时，处理请求则需要很长时间。
SERVER_POOL_TASKS=100 (This specifies 100 worker threads -- the new R5 mechanism for actually carrying out the database work of all connected users.)
SERVER_POOL_TASKS=100（指定 100 个worker线程 ——这个新的R5机制实际承载所有连接用户的数据库工作。）
A key problem with this model is that increasing the number of worker threads increases the contention on the work queue (this is shown in Figure 3).
对于该模型的一个关键问题是增加工作线程数会加剧对工作队列的争用(如图3所示)。
This is because during the five seconds that the first timer event was sleeping, the timer kept on generating Elapsed events on different worker threads.
这是因为在这5秒期间第一个定时器事件正在睡眠，而定时器却在不同的工作者线程上继续产生时间消失事件。
Blocking worker threads and poor service deployment and distribution can significantly degrade the performance of an overall middleware infrastructure.
阻塞工作线程和不当的服务部署与分配可能会极大地降低中间件基础设施的总体性能。
Blocking worker threads and poor service deployment and distribution can significantly degrade the performance of an overall middleware infrastructure.
阻塞工作线程和不当的服务部署与分配可能会极大地降低中间件基础设施的总体性能。
应用推荐