Each CPU has a dedicated run queue.
每个CPU都有一个专门的运行队列。
This automatically places the thread on the global run queue.
这样一来，就会自动地将线程放入到全局运行队列中。
This results in the process getting moved off from the CPU run queue.
这样会将进程从CPU运行队列中移除。
There is also an additional global run queue where new threads are placed.
还有一个附加的全局运行队列，其中放的是新的线程。
A run queue is a list of runnable threads, sorted by thread priority value.
运行队列是由运行线程所组成的列表，按照线程优先级的值进行排序。
The run queue, which holds an ordered list of processes waiting to run, is another queue.
另一个队列是运行队列，其中包含等待运行的进程的有序列表。
TASK_RUNNING: the process is either running on CPU or waiting in a run queue to get scheduled.
TASK_RUNNING：进程当前正在运行，或者正在运行队列中等待调度。
All fixed priority threads will be placed on the run queue if you change the default from 0 to 1.
如果您将缺省值从0更改为1，那么所有固定优先级的线程都将放入到这个运行队列中。
When a CPU is ready to dispatch a thread, the global run queue is checked before any of the others.
当CPU准备分派线程时，它会先检查全局运行队列，然后再检查其他队列。
AIX automatically tries to encourage processor affinity by having one run queue per CPU, which was discussed earlier.
AIX会在每个CPU上都设置一个运行队列，以此来自动尝试推动处理器关联性的建立，这一点我在前面已经讨论过。
Each CPU on a system has its own dedicated run queue, which is a list of runnable threads sorted by thread priority value.
系统上的每个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.
在CPU受限的系统中，所有处理器都是100%忙碌的，并且一些作业可能正处在运行队列中等待CPU时间。
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.
对于每个虚拟处理器，可以分配0.1到1.0个物理处理器以执行虚拟处理器运行队列中的任务。
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.
还请记住，配置太多页面清洗器可能会损害数据库服务器上的运行队列，并导致极大的性能下降。
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).
但是与之前的Linux调度器不同，它没有将任务维护在运行队列中，CFS维护了一个以时间为顺序的红黑树(参见图1)。
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.
通常来说，如果某个系统的CPU是100%忙碌，并且相对于CPU的数目来说拥有大规模的运行队列，以及具有更为频繁的上下文切换，那么该系统很有可能成为CPU受限系统。
With run time for most applications lasting days or weeks, the queue fills up quickly.
由于大多数应用程序的运行时间要持续数天或数周，队列很快就满了。
In bindings mode, a JMS application must run on the same host machine as the queue manager, and they will communicate using Inter-Process Communication (IPC) protocols.
在绑定模式中，JMS应用程序必须在与队列管理器相同的主机上运行，它们将使用进程间通讯(IPC)协议进行通信。
Only two queue manager instances can run at the same time: an active instance and a standby.
只有以下两个队列管理器实例可以同时运行：活动实例和备用实例。
By choosing this option all channels within the queue manager will run as trusted.
通过选择此选项，队列管理器中的所有通道都将作为受信任应用程序运行。
If an attempt is made to start another instance, the user would receive the response that the queue manager instance is not permitted to run as a standby.
如果用户企图启动另一个实例，将收到一个响应，表明该队列管理器实例不允许作为备用实例运行。
Collections run one at a time, starting with the first one in the queue.
收集每次运行一个，从队列中的第一个收集开始。
You need not run this command on the same server where you created the queue manager; you can run this command on any server where that queue manager is defined.
不需要在创建这个队列管理器的服务器上运行这个命令；可以在定义了这个队列管理器的任何服务器上运行这个命令。
This is intentional, do not change these. The queue manager will fill in the correct values at run time for you.
这是故意为之，不要更改它们，队列管理器将在运行时填充正确的值。
The run time server retrieves the message from the JMS queue and populates the appropriate intermediate objects with the values contained in the event payload.
运行时服务器从JMS队列检索消息，并使用事件有效负载中包含的值填充适当的中间对象。
Transfer this file to the server where the coordination queue manager is created and run it against the queue manager.
将此文件传输到创建了协调队列管理器的服务器，并在队列管理器中运行。
Once the message is delivered on the queue, run the JMS receiver client to retrieve it.
消息传递到队列上之后，请运行JMS接收方客户机以检索消息。
I use the PHP command-line interpreter to run that script and put the method call into the queue.
我使用PHP命令行解释器运行这个脚本，并将这个方法调用放进队列中。
If your application requires messages to be returned from the remote queue manager, you need to define another channel to run in the opposite direction between the queue managers.
如果您的应用程序要求从远程队列管理器上返回消息，则需要在两个队列管理器之间定义另一个相反方向的通道。
It is reasonable to leave days between migrating each queue manager in the cluster, in order to test applications before wholly committing all queue managers to run at the new version.
在迁移集群中的各个队列管理器之间最好间隔几天，以便在所有队列管理器完全在新版本下运行之前测试应用程序。
应用推荐