每个CPU都有一个专门的运行队列。
内存和用户数量对运行队列长度的影响。
另外，还有一种运行队列，称为全局运行队列。
There is also another run queue called the global run queue.
所有新线程都被放在全局运行队列中。
还有一个附加的全局运行队列，其中放的是新的线程。
There is also an additional global run queue where new threads are placed.
这样会将进程从CPU运行队列中移除。
This results in the process getting moved off from the CPU run queue.
运行队列管理器的节点还必须在内部磁盘上维持许多文件。
A node running a queue manager must also maintain a number of files on internal disks.
另一个队列是运行队列，其中包含等待运行的进程的有序列表。
The run queue, which holds an ordered list of processes waiting to run, is another queue.
这样一来，就会自动地将线程放入到全局运行队列中。
This automatically places the thread on the global run queue.
这是一个绝妙的解决方案，可以避免维护按优先级调度的运行队列。
That's an elegant solution to avoid maintaining run queues per priority.
如何改变我的后台操作优先使用或运行队列的动态调度。
How can I change the background operation priority dynamically using Dispatch or operation queues.
一个从非空运行队列的前端分派的线程具有最高的优先级。
A thread is dispatched from the front of the nonempty run-queue with the highest priority.
运行队列是由运行线程所组成的列表，按照线程优先级的值进行排序。
A run queue is a list of runnable threads, sorted by thread priority value.
TASK_RUNNING：进程当前正在运行，或者正在运行队列中等待调度。
TASK_RUNNING: the process is either running on CPU or waiting in a run queue to get scheduled.
结果是空闲处理器只能等待这个处理器释放出运行队列锁，这样会造成效率的降低。
The result was idle processors awaiting release of the runqueue lock and decreased efficiency.
当CPU准备分派线程时，它会先检查全局运行队列，然后再检查其他队列。
When a CPU is ready to dispatch a thread, the global run queue is checked before any of the others.
逻辑上可将系统看作：为(40个中的)每个优先级管理一个fifo序列，称为运行队列。
Logically, you can view the system as managing a single FIFO queue, termed a run-queue, for each of the 40 priorities.
还请记住，配置太多页面清洗器可能会损害数据库服务器上的运行队列，并导致极大的性能下降。
Also keep in mind that having too many page cleaners may overwhelm the run queue on the database server and cause the significant performance degradation.
如果您将缺省值从0更改为1，那么所有固定优先级的线程都将放入到这个运行队列中。
All fixed priority threads will be placed on the run queue if you change the default from 0 to 1.
当一个执行线程超过它的时间量时，它的优先级被放在运行队列的后端并给它指定了新的时间量。
When an executing thread expires its time quantum, it's placed at the end of the run-queue for its priority and assigned a new time quantum.
运行队列的前 100 个优先级列表保留给实时任务使用，后 40 个用于用户任务（参见图1）。
The first 100 priority lists of the runqueue are reserved for real-time tasks, and the last 40 are used for user tasks (see Figure 1).
系统上的每个CPU都有自己专用的运行队列，该队列是按线程优先级值排序的可运行线程的列表。
Each CPU on a system has its own dedicated run queue, which is a list of runnable threads sorted by thread priority value.
对于每个虚拟处理器，可以分配0.1到1.0个物理处理器以执行虚拟处理器运行队列中的任务。
For each virtual processor, between 0.1 and 1.0 physical processor can be dispatched to execute tasks in that virtual processor's run queue.
在CPU受限的系统中，所有处理器都是100%忙碌的，并且一些作业可能正处在运行队列中等待CPU时间。
In a system that is CPU-bound, all the processors are 100 percent busy and some jobs might be waiting for CPU time in the run queue.
因为线程执行的是相同的代码，所以它们应作出类似的动态优先级调整并在相同的运行队列中轮替执行。
Because the threads execute identical code, they should have similar dynamic priority adjustments and execute in a round-robin fashion from the same run-queues.
AIX会在每个CPU上都设置一个运行队列，以此来自动尝试推动处理器关联性的建立，这一点我在前面已经讨论过。
AIX automatically tries to encourage processor affinity by having one run queue per CPU, which was discussed earlier.
除了CPU的运行队列(称为活动运行队列(activerunqueue))之外，还有一个过期运行队列。
In addition to the CPU's runqueue, which is called the active runqueue, there's also an expired runqueue.
但是与之前的Linux调度器不同，它没有将任务维护在运行队列中，CFS维护了一个以时间为顺序的红黑树(参见图1)。
But rather than maintain the tasks in a run queue, as has been done in prior Linux schedulers, the CFS maintains a time-ordered red-black tree (see Figure 1).
proc/sched_debug：显示运行时调度程序可调优选项的当前值、CFS统计信息和所有可用CPU 的运行队列信息。
proc/sched_debug: Displays the current values of runtime scheduler tunables, the CFS statistics, and runqueue information on all available CPUs.
通常来说，如果某个系统的CPU是100%忙碌，并且相对于CPU的数目来说拥有大规模的运行队列，以及具有更为频繁的上下文切换，那么该系统很有可能成为CPU受限系统。
Generally speaking, a system has an excellent chance of becoming CPU-bound if the CPU is 100 percent busy, has a large run queue compared to the number of CPUs, and more context switches than usual.
应用推荐