如果某个线程被这样一个任务永久地消耗着，那么它实际上就被从池除去了。
If a thread is permanently consumed with such a task, it has effectively been removed from the pool.
要有效地调整线程池大小，您需要理解正在排队的任务以及它们正在做什么。
To tune the thread pool size effectively, you need to understand the tasks that are being queued and what they are doing.
乍看之下，它似乎是另外一种线程池，但它却支持任务之间的父子关系。
At first glance this is just another thread pool, but it supports parent-child relationships between tasks.
如果您要自己创建线程来处理生存期很短的任务，那么您绝对应该考虑使用线程池来替代。
If you find yourself creating threads to handle short-lived tasks, you should definitely consider using a thread pool instead.
线程池的最佳大小取决于可用处理器的数目以及工作队列中的任务的性质。
The optimum size of a thread pool depends on the number of processors available and the nature of the tasks on the work queue.
任务并行库，又被称为TPL，本质上是一个高级版本的。NET线程池。
The Task Parallel Library, or TPL, is essentially an advanced version of the.net thread pool.
相反，当没有任务要完成时，固定大小的线程池会让所有的线程等待。
In contrast, the fixed-size pool keeps all the threads around waiting for something to do when there are no tasks to complete.
它为与新的pbuf池相关的管理任务提供了支持。
It provides support for new pbuf pool-related administrative tasks.
最新的eventMPM是一种实验性的模型，为不同的任务使用单独的线程池。
The final, event MPM is an experimental module that keeps separate pools of threads for different tasks.
但是实际上，操作系统需要用这4GB内存的一部分处理映射和其他内存池，这是它运行的所有LotusDomino任务所需要的。
The operating system actually needs some of this 4 GB of memory for mapping and other memory pools for all the Lotus Domino tasks that it runs.
TPL还拥有一套从前的线程或线程池所不具备的新功能，例如任务拥有一个安全的Cancel方法。
The TPL also has a new set of features not seen in either threads or thread pools. For example, Tasks have a safe Cancel method.
可以创建ThreadPoolStatusMBean，提供处理这些任务所使用的线程池的管理接口，并把它用JMX注册。
You can create a ThreadPoolStatus MBean to provide the management interface for the thread pool used to process these tasks and register it with JMX.
GPars还定义通过线程池(比如actors)调度的逻辑数据流任务并通过数据流变量进行传输。
GPars also defines logical dataflow tasks that are scheduled over a thread pool (like actors) and communicate via dataflow variables.
我们已经探究了如何使用GPars将任务推入Executor池的机理。
We've already explored the mechanics of how to push tasks into an Executor pool with GPars.
WebSphereApplicationServer旨在处理大量的并行短时间任务，工作队列和线程池是两个经常用来处理并行工作负载的组件。
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.
由于GPars将这些任务分配给了一批作业员，我现在可以并行执行我的所有搜索了(只要内存池足够大)。
Because GPars gives these tasks to a pool of workers, I can now perform all of my searches in parallel (provided the pool is large enough).
如果Informix存储池未填满，或出于其他原因不能成功添加块，则任务失败。
If the Informix storage pool is not populated or, for whatever reason, cannot successfully add a chunk, the task fails.
试图向池线程传递任务的调用者都会发现池为空，在调用者等待一个可用的池线程时，它的线程将阻塞。
Any caller that attempted to pass a task to a pool thread would find the pool empty, and its thread would block while it waited for an available pool thread.
有了从监控任务中收集的缓冲池运行时统计数据，您就可以知道是否任何性能获益都可以从缓冲池调优实现。
With the buffer pool runtime statistics gathered from the monitoring tasks, you can see whether any performance gain can be achieved from buffer pool tuning.
各种类型的线程池中一个严重的风险是线程泄漏，当从池中除去一个线程以执行一项任务，而在任务完成后该线程却没有返回池时，会发生这种情况。
A significant risk in all kinds of thread pools is thread leakage, which occurs when a thread is removed from the pool to perform a task, but is not returned to the pool when the task completes.
HTTP任务本身能够使用池，所以默认的40个HTTP线程能够支持几千个用户。
The HTTP task itself is able to do the pooling, so the default of 40 HTTP threads can support several thousand users.
总的来说，通用的最佳实践是确定哪些线程池服务任务需要DataSource连接并相应调节池的大小。
Overall, the general best practice is to determine which thread pools service tasks that require a DataSource connection and to size the pools accordingly.
你不能同时运行的线程池线程两个并发任务。
You cannot run two concurrent Tasks in the same thread-pool thread.
使用传统的线程池来实现fork-join也具有挑战性，因为 fork-join任务将线程生命周期的大部分时间花费在等待其他任务上。
Using conventional thread pools to implement fork-join is also challenging because fork-join tasks spend much of their lives waiting for other tasks.
内存池的大小和QZDASOINI任务所在内存池的最大活动级别。
The memory pool size and the Max activity level values for the memory pool where QZDASOINIT jobs are running.
返回可识别此线程池的字符串及它的状态，包括运行状态、并行级别、工作线程和任务数量。
Returns a string identifying this pool, as well as its state, including indications of run state, parallelism level, and worker and task counts.
返回可识别此线程池的字符串及它的状态，包括运行状态、并行级别、工作线程和任务数量。
Returns a string identifying this pool, as well as its state, including indications of run state, parallelism level, and worker and task counts.
应用推荐