The global lock cache feeds the per-thread lock caches.
全局锁缓存将其内容提供给单线程锁缓存。
Using ThreadLocal makes sense when you need to store variable instances on a per-thread basis.
当您需要以线程为单位存储变量实例时，使用ThreadLocal 很有意义。
You can use ThreadLocal variables to store any sort of per-request context information using the per-thread-singleton technique described earlier.
您可以通过前面讲述的每线程单子技术用ThreadLocal变量来存储各种每请求(per - request)上下文信息。
To help minimize mutex allocation and locking time, the JVM manages a global lock cache and a per-thread lock cache where each cache contains unallocated pthread_mutexes.
为了帮助实现互斥锁分配和锁定时间的最小化，JVM管理一个全局锁缓存和一个单线程锁缓存，其中每个缓存包含了未分配的 pthread_mutex。
HP-UX 11.31 has per-thread locks and as such there are significant performance enhancements with the latest version of HP-UX — up to 30% more performance compared to 11iv2.
HP -UX 11.31具有每线程锁，因此HP - UX的最新版本的性能显著提高了——与11iv2相比，最多能够提高30%。
设置每个线程断点。
This initial call ensures that the per-thread initialization can complete without deadlock.
此初始调用确保在不死锁的情况下，完成每个线程初始化。
Per-thread method activation stacks are represented using the host operating system's stack and thread model.
每线程方法的激活栈使用主机操作系统的堆栈和线程模型。
On AIX, this uses at least 256KB per thread.
在AIX 上，每个线程至少需要使用 256KB。
OpenSessionInView interceptor and filter which allow the usage of the same session per thread across different components.
OpenSessionInView拦截器和过滤器允许每个线程跨不同组件使用同一会话。
Thus it is relatively straightforward to implement the classic one thread per connection model.
因此实现典型的每个连接一个线程的模型便非常简单。
If synchronous and asynchronous requests are allowed to be submitted concurrently, this situation can mean supporting at least one more thread consumption (for the Ajax request) per user request.
如果允许并发地提交同步和异步请求，就意味着每个用户请求至少要支持多出一个的线程消耗(用于Ajax请求)。
If they are joinable threads and you haven't called the pthread_join to join them, each produced thread will leak a sizeable amount of memory (at least 10mb per stack) after its termination.
如果它们是可接合的线程，且您没有调用pthread_join来联接它们，那么在线程终止后，每个产生的线程都将泄漏大量的内存(至少每堆栈10MB)。
Allocated per thread, when needed.
当需要时，会分配给每个线程。
This approach is a little more limited, because it does not give you stateless performance — you are in fact using a separate thread per user.
这种方式有一点儿受限制，因为它不提供无状态性能——实际上是为每个用户使用一个单独的线程。
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个工作线程。
Instead of allocating one thread per open socket, we place all requests into a generic queue serviced by a set of RequestHandlerThread instances.
不是为每个打开的socket分配一个线程，相反，我们把所有请求放到一个由一组RequestHandlerThread实例所服务的通用队列中。
This in turn results in one thread per user on Tomcat, while the NIO server handles the same load with a constant number of threads.
然后它导致了在Tomcat上为每个用户分配一个线程，而NIO 服务器用固定数量的线程来处理相同的负载。
Because some processing can take a long time, we need multiple processing threads per production line to make sure that a thread is always available to work on the latest measurement.
由于某些处理可能要占用较长的时间，因而需要为每条生产线使用多个处理线程，确保总有一个线程能来处理最新的度量结果。
Texture baking using multiple threads: You can use the Bake Optimization feature to select between baking using one thread per object or baking using multiple threads per object.
多线程烘焙贴图：你可以使用烘焙优化特性来选择是每个物体使用一个线程烘焙还是每个物体多线程烘焙。
Although the amount of memory used per thread is quite small, for an application with several hundred threads, the total memory use for thread stacks can be large.
虽然每个线程使用的内存量相当少，但对于拥有几百个线程的应用程序，线程栈的内存使用总量会达到很高。
This breaks the one thread per request model, as the thread for a request never gets freed up.
这打破了每个请求使用一个线程的模型，因为用于一个请求的线程一直没有被释放。
A global thread (per server process) is responsible for creating and managing each user connection thread.
一个全局线程(每个服务器进程一个)负责创建和管理用户连接线程。
An alternative is to tie up the thread per request so that it can be returned to the thread pool once the request processing is done.
另一种方法是为每个请求绑定一个线程，因此当请求被处理后，线程将返回线程池。
This depends on your ability to recognize the methods and classes in question, not to recognize the thread itself, per se.
从本质上讲，这取决于您识别有问题的方法和类的能力，而不是识别线程本身。
At first, it may feel like the spawned thread isn't responding to the messages quickly enough, but remember, in an actors model, you don't deal with threads, per se, just message passing.
初看上去，似乎是生成的线程无法足够快地响应消息，但是要记住在actor模型中并不处理线程，只处理消息传递。
The POWER7 processor can also now house eight processing cores-four times the number of cores in older POWER6 processor-based servers, with each core capable of executing four tasks per thread.
POWER 7处理器现在还可以提供8个处理器核，这是基于POWER 6处理器的老式服务器的4倍，一个核每个线程能够执行4个任务。
This is what is very different from the "one thread per request" which has been prevalent until now.
这与现在大行其道的“一个请求一个线程”有着很大的差别。
Similarly, you can create a pool of parsers-one per thread-at initialization time.
类似地，在初始化期间可以创建一个解析器池(每个线程创建一个)。
Similarly, you can create a pool of parsers-one per thread-at initialization time.
类似地，在初始化期间可以创建一个解析器池(每个线程创建一个)。
应用推荐