This means that there are 5 parallel CSLD task threads.
这意味着有5个并行的CSLD任务线程。
This is why we need to understand how to increase the number of parallel CSLD task threads so that more CM agents can be used by archpro.
正因为如此，我们需要理解如何增加并行CSLD任务的数量，以便archpro可以使用更多的CM代理。
Instead of setting a parameter in some configuration document, you need to analyze the environment and design the setup so that parallel CSLD task threads are possible.
这不是仅仅通过设置某种配置文档中的一个参数就可以完成的，而是需要对环境进行分析，设计设置，使并行CSLD任务线程成为可能。
If there is just one CM agent configured, archpro could become a bottleneck since this one agent would need to serialize the archiving operations requested by the four parallel CSLD task threads.
如果只配置了一个CM代理，那么archpro可能成为一个瓶颈，因为这一个代理需要串行地处理由4个并行的CSLD任务线程请求的归档操作。
Obviously, realistic weightless threads should do something, and this will use some greater resources proportionate to the task.
显然，真正的轻便线程应该做一些事情，而这将根据任务使用更多的资源。
Accommodate one or more threads working together to accomplish a task.
提供一个或多个协作完成一项任务的线程。
Also, if the process or task instances are deleted by two threads simultaneously, this results in error messages in the logs.
另外，如果两个线程同时删除过程或任务实例，会导致在日志中记录错误消息。
The threads are automatically started by the CSLD task and will run in parallel.
这些线程是由CSLD任务自动启动的，并且并行地运行。
Due to the heavy load on the database system, it does not make sense to have several threads cleaning the process or task instances at the same time.
由于会在数据库系统产生很重的负载，同时用多个线程清理过程或任务实例是没有意义的。
Parallelism is introduced by running the main thread scheduling child threads for each task so that the tasks execute concurrently while each thread execute the task synchronously.
并行性是通过运行主线程为每一个任务调度执行的子线程而实现的，这样任务就会并发执行，而每一个线程是同步执行任务的。
A task is a collection of threads and access rights to memory objects and ports.
任务是存储对象和端口的线程和访问权限的集合。
For educational purposes, we've split this task among three threads: one prints the first name, one prints a space, and one prints the surname and a new-line.
出于教学目的，我们把此任务分在三个线程中：一个线程打印人名，一个线程打印空格，一个线程打印姓和一个新行。
The HTTP task itself is able to do the pooling, so the default of 40 HTTP threads can support several thousand users.
HTTP任务本身能够使用池，所以默认的40个HTTP线程能够支持几千个用户。
Changed the number of threads in the server task.
更改服务器任务中的线程数。
A "task" is an object consisting of a set of system resources that enable "threads" to run.
“任务”是“线程”运行所需若干系统资源组成的一个对象。
Unlike traditional systems, under Mach a process, or "task", can consist of a number of threads.
Mach的进程——或者叫“任务”——有别于传统的操作系统，可以由很多的线程组成。
These threads are fixed in number until you change the value in the Server document, and then restart the HTTP task.
在更改Server文档中的值并重启HTTP任务之前，这些线程的数量是固定的。
When starting the CSX task in a command window, the parallel CSX worker and committer threads are listed as depicted in Figure 8.
当在一个命令窗口中开始CSX任务时，并行csxworker线程和committer线程将被列出来，如图8所示。
To optimize the CommonStore throughput, it is necessary to configure the CommonStore task so that it runs with parallel threads.
为了优化CommonStore吞吐量，需要配置 CommonStore任务，使之以并行的线程运行。
If the task is started in a command window, the individual threads become visible as depicted in Figure 5.
如果在一个命令窗口中开始任务，则可以看到各个线程，如图5所示。
In this application you will perform this kind of task-accessing multiple remote Web services simultaneously using the multiple threads through the Workers API.
在本应用程序中，我们将需要执行这一类任务—通过WorkersAPI用多个线程同时访问多个远程Web服务。
Now that we have a little basic background on threads, let's discuss how we can correctly use threads that best suits our task at hand.
既然已经有了些线程的基本知识，我们来讨论下如何正确的使用最适合手头工作的线程。
Threads represent the ability to execute units of a process or task in parallel. A process can have many threads, each of which is weak to the process.
线程代表平行执行处理或任务的能力。处理可以有很多个线程，每个线程都会减弱处理。
The task parallel model is built around the idea that parallelism can be extracted by constructing threads that each have their own goal or task to complete.
任务并行模型是建立在并行想法可以提取的建设，每个线程有自己的目标或完成的任务。
We can use the technology specialized in the thesis to make the threads to communicate so as to complete the task.
可以按照文中介绍的技术使这些线程通信以完成特定任务。
Since deleting an ACE_Task object doesn't shut down any active threads, the threads must therefore exit before the task object can be deleted.
因为删除ACE_Task对象并不结束任何一个活动线程，线程必须结束在任务对象被删除前。
Once a thread in the pool completes its task, it is returned to a queue of waiting threads, where it can be reused.
一旦集区中的执行绪完成工作，就会回到等待中执行绪的伫列，执行绪可以在这里被重复使用。
Once a thread in the pool completes its task, it is returned to a queue of waiting threads, where it can be reused.
一旦集区中的执行绪完成工作，就会回到等待中执行绪的伫列，执行绪可以在这里被重复使用。
应用推荐