调用此函数从I /O处理器线程上下文，因此应该采取一种方式，它消耗最少量的时间，相同的线程处理多个会话执行。
This function is invoked from the I/O processor thread context, hence should be implemented in a way that it consumes minimal amount of time, as the same thread handles multiple sessions.
对于绑定连接，您将看到每个处理器或许有4到5个线程。
For bindings connections, you should look for maybe 4 to 5 threads per processor.
可为所产生的每个数据片段生成一个新线程，但这会将大量处理器时间浪费在启动和停止线程上。
We could spawn a new thread for each piece of data produced, but this would waste a lot of processor time starting and stopping threads.
然而，我们仍旧运行在一个处理器上，即使两个线程真的可以同时执行，物理法则也是不允许的。
However, we were still running on a single processor and even if two threads could really execute simultaneously, physical laws prevented it.
处理器利用率不是调整线程池大小过程中的唯一考虑事项。
Processor utilization is not the only consideration in tuning the thread pool size.
在POWER 5芯片中，每个处理器中有两个硬件线程。
On POWER5 chips, there are two hardware threads on each processor.
例如，您可以将线程绑定到给定的处理器，以找出导致某个挂起程序的根源。
For example, you can bind threads to a given processor to find the root cause of a hanging program.
理想情况下，线程的数量应该根据处理器的数量和请求的长度或持续时间进行调整。
Ideally, the number of threads should be tuned based on the number of processors and the length or duration of each request.
物理处理器将负责处理这两个线程之间的同步问题。
The physical processor takes care of synchronization issues between the two threads.
当这个配置参数被启用时，数据库服务器自动调整AIO虚拟处理器和清理线程的数量，并自动调优 LRU刷新。
When this configuration parameter is enabled, the database server automatically adjusts the number of AIO virtual processors and cleaner threads, and automatically tunes LRU flushing.
理想的情况是，线程数量等于处理器的数量，不过这也要求任何线程都不应该执行诸如同步读写、等待事件通知等阻塞型的操作，以免线程阻塞。
The ideal number is one per processor, but that implies that none of these threads should execute a blocking operation such as a synchronous read/write or a wait on an event.
处理器中的线程是一种设计技术，允许两组或多组指令同时执行，从而提高性能。
Threading within a processor is a design technique used to improve performance by permitting what appears to be the simultaneous execution of two or more sets of instructions.
在内核中，这些进程称为线程，代表了单独的处理器虚拟化(线程代码、数据、堆栈和CPU寄存器)。
In the kernel, these are called threads and represent an individual virtualization of the processor (thread code, data, stack, and CPU registers).
例如，处理器的亲缘性(affinity)决定了一个线程能够运行在哪个处理器上，它被表示为32位或64位整数的位掩码。
For example, processor affinity, which determines which processors a thread can run on, is expressed as a 32 - or 64-bit integer acting as a bitmask.
prev和intpri字段中的值帮助判断处理器是在运行线程还是在运行中断处理程序。
The values in the prev and intpri fields help in determining whether the processor is running a thread or an interrupt handler.
通过在与包含所需数据的内存处于相同pod中的处理器上调度线程，服务器可以保证性能优势。
The server can see performance benefits by scheduling threads on processors that are in the same pod as the memory that contains the data that's needed.
NTPerfMon实用工具对这一指标的定义如下：“%TotalProcessortime指系统上所有处理器执行非空闲线程的平均时间百分比。”
The nt PerfMon utility defines this metric as follows, "the % Total processor time is the average percentage of time that all the processors on the system are busy executing non-idle threads."
在多处理器系统中，Linux试图模拟分派到可用处理器的单个全局RT线程队列的行为。
On multiprocessor systems, Linux tries to emulate the behavior of a single global queue of RT threads that are dispatched to available processors.
如果此程序在单处理器或卸载的多处理器上运行，则每个线程打印的for循环迭代计数大致相同。
If this program is run on a uniprocessor or unloaded multiprocessor system, each thread prints out close to the same for loop iteration count. In one run, the program printed.
与一个CPU运行多个操作系统线程、服务多个用户一样，一个Informix虚拟处理器运行多个线程，服务多个SQL客户机应用程序。
Just as a CPU runs multiple operating system processes to service multiple users, an Informix virtual processor runs multiple threads to service multiple SQL client applications.
从本质上讲，任何进程或线程都可以分派到任意处理器上运行，但绑定在特定处理器上运行的处理器或线程除外。
Essentially, any process or thread can be dispatched to run on any processor, except for processors or threads that are bound to run on a specific processor.
如果没有其他的线程可供执行，那么处理器就将空闲。
If no other threads are available for execution, then processors may sit idle.
如果线程数多于处理器数，那么线程必须争用处理器时间，有些线程会一直处于等待状态，这样，应用程序的效率就降低了。
Once there are more threads than processors, the threads must compete with one another for processor time, and some threads will always be waiting, so the application effectiveness is reduced.
这个回调处理器类拥有两个线程本地变量，用于存储来自客户端实例的用户ID和密码。
The callback handler class has two thread local variables that can store the user ID and password from the client instance.
因为POWER 5能识别多线程，因此它可以区分相同或不同处理器上的线程。
Because the POWER5 is multithreading-aware, it can distinguish between threads on the same or different processors.
在POWER 5中，对于每个处理器，您最多可以拥有两个同步多线程的线程。
In POWER5, you can have a maximum of two Simultaneous Multi-Threading threads per processor.
与线程池的功能类似，TPL能够在线程和处理器之间实现负载均衡。
Like a thread pool, the TPL can perform load balancing across threads and processors.
该分析工具也适用于在单处理器上运行多线程应用程序。
The analysis can also be applied to multi-threaded applications running on a single processor.
该分析工具也适用于在单处理器上运行多线程应用程序。
The analysis can also be applied to multi-threaded applications running on a single processor.
应用推荐