Typically, the source device can't maintain a high enough transfer rate to keep the CPU busy.
典型情形是，源设备不能保持足够高的传输速率以使得CPU 保持繁忙。
Captured CPU time is the CPU busy time that the operating system can reliably attribute to a given address space.
捕获的CPU时间是操作系统能可靠地用于一个特定的地址空间的 CPU 被占时间。
Now that we can keep a CPU busy for a while, we'll see how to set a priority for a process. To summarize what we've learned so far
现在我们可以让CPU 持续忙碌一段时间，我们了解如何设置进程的优先级。
While customers typically gather CPU resource utilization Numbers, such as CPU busy, they typically do not collect and manage their Domino statistics.
虽然客户通常将CPU资源利用率数字(比如cpu忙)收集在一起，但他们通常不收集和管理他们的Domino统计数字。
Our thread is sleeping, waiting for a particular condition to become true, without performing any kind of busy polling that would waste CPU time.
线程将一直睡眠，直到特定条件发生，在这期间不会发生任何浪费CPU时间的繁忙查询。
For each CPU, it shows the percentage of time the CPU was idle, the percentage of time the CPU was busy, and the percentage of time the CPU spent handling interrupts.
为每个CPU显示出了CPU空闲所占的时间百分比、CPU繁忙所占的时间百分比以及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时间。
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受限系统。
No, the percentage of time that the CPU spends handling interrupts is not a subset of the total busy time for that CPU.
不包括。CPU处理中断所占的时间百分比并不是那个 CPU全部繁忙时间的子集。
If you discover that the system keeps the CPU 100 percent busy, you need to investigate the process that causes this situation.
如果发现系统使CPU保持100%忙碌，则需要调查导致这种情况发生的进程。
The CPU percent busy reflects the information that is displayed in figure 3.
CPU繁忙百分比反映了图3中显示的信息。
We see that the percent busy CPU tracks very closely for the three test cases from 1,000 to 4,000 virtual users.
我们看到，从1,000到4,000个虚拟用户，这三个测试用例的CPU繁忙百分比非常接近。
Figure 1 shows the percent busy CPU for the AIX platform.
图1显示AIX平台的CPU繁忙百分比。
So several factors can cause slowdowns: the CPU is busy, the application is doing too much I/O, it is waiting for I/O to complete, or some combination.
所以有多个因素可能导致速度降低：CPU繁忙、应用程序做的I/O过多、等待 I/O完成或上述情况的某种组合。
Does the percentage of time the CPU is busy include the percentage of time the CPU is handing interrupts?
CPU繁忙所占的时间百分比是否包括CPU处理中断所占的时间百分比？
As a result, the operating system is too busy paging to give the application server the required CPU time.
导致运行的系统过度繁忙而无法给应用服务器所需的CPU时间。
It's unfortunate, but keeping the CPUs busy makes up for the problem of a CPU cache being cold for a migrated task.
不幸的是，保持CPU繁忙会出现CPU缓存对于迁移过来的任务为冷的情况。
If you suspect that the problem is due to a large or overly busy process, then you should check the output of the ps tool, look for the process size, the percentage of memory, and CPU being utilized.
如果您怀疑是一个大型的或过度繁忙的进程导致了该问题，那么您应该检查ps工具的输出，查找进程大小、内存百分比和cpu利用率。
Percentage of time the CPU is busy.
CPU繁忙所占的时间百分比。
When binding a process to a CPU, you can actually reduce performance for that process if the CPU to which the process will be bound is busy while others are idle.
在将进程绑定到CPU 时，如果该 CPU正处于繁忙状态，而其他 CPU 却处于空闲状态，则绑定操作实际上会降低该进程的性能。
If the percent busy is close to or at 100 percent, then the CPU could be limiting the system.
如果CPU使用率接近100%，则系统会受到CPU的限制。
The busy strategies activate metering when a thread or managed process exhibit consistently high CPU usage for a specified period.
Busy策略下，当一个线程或被管理流程在某一指定周期内CPU使用率一直处于高位时对活动进行计量。
The busy strategies activate metering when a thread or managed process exhibit consistently high CPU usage for a specified period.
Busy策略下，当一个线程或被管理流程在某一指定周期内CPU使用率一直处于高位时对活动进行计量。
应用推荐