The percent CPU improvement for Domino 7 on all platforms varied by the number of active users.
在所有平台上，Domino7的CPU 性能提高百分率随活动用户数的变化而不同。
NTF mail template at 4000 users used 49.2 percent CPU, with average response time of 0.100 seconds.
Domino 7使用mail7 . ntf邮件模板在4000个用户时使用49.2 %的CPU资源，平均响应时间为0.100秒。
'ps -aux' to collect process information, such as process ID, percent CPU, and virtual memory footprint.
'ps- aux '用于收集进程信息，例如进程ID、CPU百分比以及虚拟内存足迹。
Document the results obtained (up to 28 percent CPU usage improvement) from our upgrade of the production DPARs.
记录从生产DPAR升级中获得的结果(多达28%的CPU使用率改善)。
Domino 6.5 at 4000 users utilized 54.8 percent CPU, with average response time of 0.123 seconds. Domino 7 with the mail6.ntf.
Domino 6.5在4000个用户时使用54.8%的CPU资源，平均响应时间是0.123秒。
This is true in both Domino 6.x and Domino 7, making percent CPU the limiting factor in the number of users that can be supported.
CPU使用百分比限制了所能支持的用户数，在Domino 6 .x和Domino7中都是这样。
mail template at 4000 users consumed 46.8 percent CPU, with average response time of 0.111 seconds; and Domino 7 with the mail7.
Domino7 使用 mail6.ntf邮件模板在 4000 个用户时占用 46.8% 的CPU 资源，平均响应时间是 0.111秒；
Figure 2 shows this reduction in percent CPU and how it allows Domino 7 to gain around 50 percent more Domino Web Access users than Domino 6.x.
图2显示了在CPU百分比方面的减少，以及这如何使Domino7比Domino 6 . x多为50%的DominoWebAccess用户提供服务。
If we can measure the power at 0-percent CPU (or as close as possible) and at 100 percent, we can assume a linear interpolation between the two.
如果我们可以测量出CPU在0使用率时(或尽可能接近0)与在100%使用率时的电量，我们就可以假设二者之间是线性关系。
As you can see, there is little CPU penalty to maintaining the index (1 percent in our test case), but a heavy search cost of 20 percent CPU usage.
可以看到，只需要很少的CPU资源来维护索引(在我们的测试用例中是1%)，但是却需要使用高达20%的CPU资源进行搜索。
Additional functionality included with the Domino 7 mail template has shown a 5 to 15 percent CPU utilization cost when running R6Mail workload tests.
Domino7邮件模板中包含的其他功能要比运行r 6Mail任务负载测试多消耗5%到15%的CPU。
However, we recommend you use Domino 7 on SLES 9 because our lab measurements show an approximately 10 percent CPU usage saving with SLES 9 over SLES 8.
然而，我们建议您在SLES9上使用Domino7，因为我们的实验室测试显示使用SLES 9可以比SLES8大约节省10%的CPU。
On two other servers, one hosting IGS users and the other users from various departments, we measured 14 percent and 23 percent CPU savings, respectively.
在另外两台服务器上(负责处理IGS用户和各个部门的其他用户)，我们测试到能分别节省14%和23%的CPU。
For our tests, consolidating users from four servers onto a single server resulted in a 10 percent CPU improvement overall, and a reduced memory footprint.
在我们的测试中，合并来自四台服务器的用户到单个服务器上，CPU总体提升10%，还减少了内存的使用。
The CPU percent showed the average of the one-hour steady state of each 1,000-user increment.
每个数据点增加1,000个用户，这里的CPU百分比是一小时的稳定状态下的平均值。
Figure 4 shows weekly CPU percent usage in this configuration.
图4显示了这种配置中每星期的CPU使用百分比。
Figure 3 shows weekly CPU percent usage in our IGS configuration.
图3显示了我们的IGS配置中每星期的CPU使用百分比。
Figure 8 shows the percent of CPU improvement from SLES 9.
图8显示了SLES 9 上CPU改进的百分比情况。
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 2 shows weekly CPU percent usage in our IBM Research configuration.
图2显示了我们的IBMResearch配置中每星期的CPU使用百分比。
The following table shows the percent of CPU improvement for Domino 7 compared to Domino 6.5.
下表显示了Domino7与Domino 6.5相比cpu性能改进的百分比。
96 percent average CPU utilization (User: 75.02 percent, System: 24.94 percent).
96%平均CPU利用率(用户：75.02%，系统：24.94%)。
Database queries can become quite intense on their own, often pegging a CPU at 100 percent for doing simple SELECT statement with reasonable size datasets.
数据库查询自身可以变得相当激烈，通常在对大小合理的数据集执行简单的SELECT语句时限定在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.
在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受限系统。
If you discover that the system keeps the CPU 100 percent busy, you need to investigate the process that causes this situation.
如果发现系统使CPU保持100%忙碌，则需要调查导致这种情况发生的进程。
Throughput flattens out as CPU utilization approaches 100 percent, as expected.
正如预期的，随着CPU利用率接近100%，吞吐量曲线逐渐变平。
In one case, a customer had a 5 percent monthly compounded growth of their DPARs' CPU utilization, translating to an almost 80 percent growth in server requirements year-over-year.
在一个案例中，一个客户的DPARCPU利用率的复合增长为每月5%，可将其换算为服务器要求每年增长80%。
IMAP users may take up to approximately 60 percent more CPU than an NRPC client.
IMAP用户可能比NRPC客户机要多占用大约60%的CPU。
While for system 325 to achieve the same number of users, it USES 65 percent of the CPU.
而系统325要实现相同的用户数，需要使用65%的CPU。
应用推荐