线程池技术现在被广泛地应用在多线程系统中。
The Thread Pool technology is widely used in many multithread applications.
在用户态的线程系统中，这意味着这个进程中的所有线程也都会阻塞。
In a userpace thread system, this means that all the threads in a process are blocked as well.
libspe的之前版本使用了一个线程系统，其中您需要调用一个线程并等待它执行完成。
Previous versions of libspe used a threaded system in which you invoked a thread and then waited for it.
新的线程系统现在已经在MacRuby代码库的实验性分支中可以找到，这个分支目标成为MacRuby下一个版本。
The new threading system is available in MacRuby's experimental branch, which is destined to become the next MacRuby version.
仅当您知道存在足够的空闲系统资源时才调整线程的数量。
Only adjust the number of threads if you know that there are enough spare system resources.
首先，它初始化这些系统类不需要线程支持来执行这些静态的初始化。
First, it initializes those system classes that don't require thread support by executing their static initializers.
在多处理环境中，线程的处理时间与可用系统资源以及与其他线程的同步有关。
In a multiprocessing environment, the processing time for a thread is related to the availability of system resources and synchronization with other threads.
如果同步时还发生锁定争用，那么性能上付出的代价会大得多，因为会需要几个线程切换和系统调用。
If the synchronization actually requires contending for the lock, the performance penalty is substantially greater, as there will be several thread switches and system calls required.
争用同步之所以慢，是因为它涉及多个线程切换和系统调用。
Contended synchronizations are slow because they involve multiple thread switches and system calls.
还有一种可能是在启动时派生一个单独的低优先级的线程，当系统空闲时再去完成初始化，不过这种方法需要特别注意处理好同步。
Another possibility is to fork a separate low-priority thread during startup to perform initialization when the system is idle, although this choice requires more care to handle synchronization.
线程消耗包括内存和其它系统资源在内的大量资源。
Threads consume numerous resources, including memory and other system resources.
如刚刚提到的，遗留应用程序的单线程特性就是遗留系统技术限制的一个例子。
The single-threaded nature of legacy application, like that just mentioned, is an example of a technical limitation of a legacy system.
内核负责完成可用CPU 间的负载优化（从线程到虚拟化操作系统）。
The kernel does its part to optimize the load across the available CPUs (from threads to virtualized operating systems).
开箱即用的实现就是。NET的线程池系统以及使用了异步上下文的框架。
Out of the box you one based on.net's thread pool system and one that USES the synchronization context framework.
除了创建和销毁线程的开销之外，活动的线程也消耗系统资源。
In addition to the overhead of creating and destroying threads, active threads consume system resources.
运行于同一个进程中的所有组件都是在UI线程中实例化的，对每个组件的系统调用也都是由UI线程分发的。
All components that run in the same process are instantiated in the UI thread, and system calls to each component are dispatched from that thread.
遗憾的是，难以评估这种系统中单个调度程序线程支持的并发数。
Unfortunately, it is difficult to estimate the amount of concurrency supported by a single dispatcher thread on this kind of system.
数据流系统仅关注数据如何在系统中流动，交由线程来决定如何有效利用多个核心。
Dataflow systems focus purely on how the data flows through the system, leaving it up to the thread scheduler to determine how to efficiently make use of multiple cores.
如果不同的部分必须同时运行，那么在类unix系统中使用进程(不是线程)。
If different parts must run concurrently, use processes (not threads) on UNIX-like systems.
组中线程的数量应该不大于系统中最深的锁层次结构的深度。
The number of threads in the group should be no larger than the depth of the deepest lock hierarchy possible in the system.
给定系统上运行的线程越多，对那些有限系统资源的需要更多，等待同步锁释放的时间越长。
The more threads running on a given system, the more demand for those limited system resources and the more time spent waiting on synchronization locks to release.
在基于RPC的分布式系统里，线程的使用非常普遍。
失控RT线程可以控制系统并阻止所有其他应用程序的运行，阻止用户登录系统等等。
Runaway RT threads can take control of the system and prevent any other applications from running, prevent users from signing on to the system, and so on.
客户端不能接收服务线程(异步调用的服务端上的线程)中发生的系统异常。
The client cannot receive system exceptions that happen in the service thread (the thread on the service side of the asynchronous invocation).
虽然对于现在系统来说非常普通，但Mach是第一个这样定义任务和线程的系统。
While this is common in modern systems, Mach was the first system to define tasks and threads in this way.
“任务”是“线程”运行所需若干系统资源组成的一个对象。
A "task" is an object consisting of a set of system resources that enable "threads" to run.
mini - httpd可以在一个系统线程中处理多个并发请求，但是在主机上占用的内存或CPU很少。
Mini-httpd handles multiple concurrent requests in a single system thread, while demanding little from its host in the way of memory or CPU.
我们尝试通过增加在Server文档中指定的活动线程数来增加系统吞吐量。
By increasing the number of active threads specified in the Server document, we tried to get more system throughput.
我们尝试通过增加在Server文档中指定的活动线程数来增加系统吞吐量。
By increasing the number of active threads specified in the Server document, we tried to get more system throughput.
应用推荐