Only a single thread is used for all these benchmarks; the synchronized classes are under no thread contention.
所有基准测试都只使用一个线程；同步的类不涉及线程争用。
If no thread is available, a new one is created, and then if the thread from the pool is idle for 60 seconds, it goes away.
如果没有可用的线程，则会创建一个新线程，然后如果线程池中的线程空闲了60秒，该线程就会消失。
Furthermore, no thread can preempt it to run another of these special routines because that other routine will run at the same IRQL.
另外，没有线程可以占先它来运行另一个这样的特殊程序，因为其他程序将运行于相同的IRQL。
Or you could write a set of detectors that verify that your J2EE code is following the appropriate restrictions, such as no Thread or Socket creation.
也许可以编写一组检测器，它们验证j 2ee代码遵守适当的限制，如不创建Thread或者Socket。
Even better, in recent JVMs, the performance cost of uncontended synchronization (when no thread attempts to acquire a lock when another thread already holds it) is quite modest.
不过现在好了一点，在最近的JVM 中，没有争用的同步（一个线程拥有锁的时候，没有其他线程企图获得锁）的性能成本还是很低的。
To make better use of CPU time, we can create a pool of NHRTs to process the data. By maintaining a pool of running threads, we have no thread startup and shutdown overhead when running.
为更好地利用CPU时间，我们可以创建一个nhrt池来处理数据，通过维护一个运行中线程的池，在运行的时候就不存在任何线程启动和停止开销了。
Thus, the thread count continues to increase, but no additional users gain access to the server.
因此，线程数量持续增加，但是没有更多用户获得对服务器的访问权。
This allows the thread to stop waiting if no messages have arrived, and check a flag to see if we should keep waiting for messages.
这将允许线程在没有消息到达的情况下停止等待，查看标志，看看是否应该坚持等待消息。
Since the default thread pool sizing was sufficient, no modifications were made to the thread pool sizing.
由于默认线程池大小已经足够，因此不需要对线程池大小进行修改。
No need to worry about a thread stalling or getting caught in an infinite loop.
也不需要担心线程停止或陷入无限循环。
When the thread is blocked, no events can be dispatched, including drawing events.
一旦线程被阻塞，所有事件都不能被分发，包括屏幕绘图事件。
With this arrangement, even if Thread B has modified the top while Thread a tries to pop, you're sure that no elements in the stack are skipped.
这样，即使线程b在线程A试图弹出数据的同时修改了堆栈顶，也可以确保不会跳过堆栈中的元素。
No new work can be processed until a worker thread has completed its transaction and is free to begin executing the next one (Figure 3 depicts this scenario).
在工作线程完成其事务并释放以执行下一个事务前，无法处理任何新工作(图3给出了此场景的图释)。
Normally.net allocates up to the minimum thread count in threads as soon as needed. From them on, no more than 2 threads per second are created until you reach the maximum thread count.
一般来说。NET会尽快在线程池中分配最少数量的线程，接着每秒钟创建最多2个线程，直到达到最大线程数量。
There seemed to be no common thread or theme to Altman's films.
奥特曼的影片似乎缺乏共同的主线或主题。
No table-wide locking is needed (or even possible) to provide thread-safety when iterating the collection.
在对集合进行迭代时，不需要表范围的锁就能提供线程安全性。
No - transient data structures have one important restriction: they can only be used from one thread.
当然不能-transient版本有一个非常重要的限制：它只能被一个线程使用。
But there is no unifying thread of how Web applications are designed and implemented.
但是它仍然没有统一的思路描述如何设计和实现Web应用程序。
Typically, this should be no more than 20-25% greater than the thread pool size in the Web container.
通常，这所增加的大小不应超过web容器中线程池大小的20—25%。
We need some way to keep thread 1 and thread 2 from doing this; some way for thread 1 to say "no one else can touch I until I'm done with it."
我们需要采取一些方法避免线程1和线程2出现上述情况；这些方法要保证线程1“在完成对i的操作前不允许其他线程对i操作”。
Because the TimerCallback function gets called on a worker thread, there are no skipped beats (assuming the availability of worker threads).
因为TimerCallback功能也是在工作者线程上被调用，没有一个跳动被跳过(假设有工作者线程可用)。
"Weak-1-lock" : If one thread is in a transaction, no other thread may enter a transaction.
“弱- 1 -锁(Weak - 1 - lock)”：如果一个线程在执行一个事务，那么没有其他的线程可以进入这个事务。
Thus there is no way another thread could ever gain access to our copy of sb.
因此其他线程无法访问当前线程的sb副本。
On some OSs, the microaccounting needed to measure thread CPU usage is always turned on, so getCurrentThreadCpuTime causes no additional performance hit.
在某些操作系统上，度量线程CPU 时间所需的microaccounting总是打开的，所以getCurrentThreadCpuTime没有额外的性能影响。
An ideal solution for this has no overhead and simply suspends the thread when a breakpoint is hit.
对于这一问题的理想解决方案应该是不引入额外开销，然后在遇到断点时将线程挂起。
If the timeout has occurred before the reader thread could acquire the mutex, then no processing need be done.
如果在读线程能够获得互斥锁之前发生了超时，那么不需要进行处理。
There is no straightforward way to make the code in Listing 1 thread-safe, making this idiom an accident waiting to happen.
没有直观的途径来使清单1中的代码是线程安全的，这使这种语言风格成为了一种等待时机发生的事故。
There is no straightforward way to make the code in Listing 1 thread-safe, making this idiom an accident waiting to happen.
没有直观的途径来使清单1中的代码是线程安全的，这使这种语言风格成为了一种等待时机发生的事故。
应用推荐