Outline the methodology used for measuring a production DPAR.
概括用于度量生产DPAR的方法学。
The server.users count shows how many users are connected to your DPAR.
users数表明有多少用户连接到您的DPAR。
Figure 13 shows the number of database replications initiated by each DPAR.
图13显示了由每个dpar初始化的数据库副本数。
Before we discuss our results, we first need to explain how to measure a production DPAR.
在我们讨论结果之前，首先需要解释一下如何度量生产DPAR。
HTTP users can expect to take significantly more CPU cycles on the DPAR than an NRPC client.
HTTP用户在DPAR上比在NRPC客户机上估计可以多占用非常多的CPU周期。
We have presented both the total CPU used by each DPAR and the CPU per active 15-minute user.
我们已经给出了每个DPAR使用的总cpu和每15分钟活动用户的CPU。
An application DPAR would be running a different workload, using calls different from a mail DPAR.
应用程序DPAR将会运行不同的工作负载，使用不同于邮件DPAR的调用。
It should be noted that the findings in this article refer to a mail DPAR and not an application DPAR.
应该注意的是，本文的结果来自一个邮件DPAR而不是一个应用程序DPAR。
Part of the active user drop can also be attributed to the attrition rate on any given DPAR over time.
部分活动用户的减少也归结于随时间的推移在任何给定dpar上的损失率。
As you can see, the user activity on the newly consolidated DPAR was much heavier than on the original DPARs.
可以看到，新合并的DPAR上的用户活动比原来的DPAR上的用户活动更繁重。
Figure 5 shows an example of an interval view of the number of Domino transactions over a three-week period for this DPAR.
图5显示了该DPAR在三周期间内的Domino事务处理数的间隔视图。
This will allow us to build a more detailed understanding of potential savings from Domino 7 for any given production DPAR.
我们还可以更详细地理解针对任何给定生产DPAR，来自Domino7的潜在节省。
Let's now discuss several charts based on data obtained from a Statrep.nsf database from an internal production DPAR at IBM.
现在基于从ibm的内部生产dpar中的Statrep . nsf数据库中获得的数据来讨论几个图表。
If no new users are added over the course of a year, a DPAR starts to lose users (they leave the company, retire, and so on).
如果一年期间没有新用户加入，DPAR就会开始损失用户(因为他们可能离职、退休等)。
To understand what happened, data was captured from all the existing DPARs and from the newly created DPAR, and then compared.
为了理解发生了什么，从所有现有的DPAR和新创建的DPAR中捕获数据，然后进行比较。
Comparing this server to our newly consolidated DPAR, you can see that the difference in the results (column 6) was even more dramatic.
将该服务器与我们最新合并的dpar相比较，可以看到结果中的差异(列6)甚至更显著了。
If they are, this can be an indication of a growing workload on your DPAR, in which case you need to plan for the additional resources.
如果确实在变化，则表明DPAR上的工作量正在增长，这种情况下，您需要为附加资源制定计划。
Simply knowing the number of registered users on a DPAR does not give you an accurate indication of the amount of resources that it USES.
只知道DPAR上的已注册用户数并不能为您提供所使用资源量的准备指示。
The Notes administrators decided to move the users with the largest databases to the newly consolidated DPAR to relieve their disk issues.
Notes管理员决定将使用最大数据库的用户移动到新合并的DPAR，以减轻磁盘负担。
Since then, we have upgraded this DPAR to beta 4 (April 29, 2005), and upgraded to the Domino 7 Gold candidate build on September 9, 2005.
从那以后，我们已经将此DPAR升级到beta4(2005年4月29日)，然后在2005年9月9日升级到Domino7Goldcandidatebuild。
What they had unintentionally done, however, was to consolidate corporate-wide every power and heavy user into the newly consolidated DPAR.
但是，他们无意间将企业范围的每个功能和重用户也合并到新合并的DPAR中了。
For example, figure 7 shows the number of mail messages delivered locally on this DPAR by mail size over a several-week period for prime shift.
例如，图7显示了在主要班次的几周期间内按邮件大小在本地通过该DPAR发送的邮件消息数。
By default, only Events are stored in this database; your DPAR statistical information is not stored there unless you enabled the Collect task.
默认情况下，该数据库只存储Events；并不存储DPAR统计信息，除非您启用了Collect任务。
DPAR 2 had 4001 registered users, 1320 active users (33 percent active), and performed an average of about 7,000,000 daily prime time transactions.
DPAR2有4001个注册用户，1320个活动用户(33%活动)，并且每天正常工作时间处理大约7,000,000个事务。
Although these volumes are much lower than the green line, the size of the message can actually cause a greater spike in CPU resources on this DPAR.
虽然这些量远远低于绿色线，但消息大小实际可以导致该DPAR上出现更大的CPU资源峰值。
The first DPAR (DPAR 1) had 3985 registered users, 1235 active users (31 percent active), and handles about 7,000,000 daily prime time transactions.
第一个DPAR (DPAR1)有3985个注册用户，1235个活动用户(31%活动)，并且每天正常工作时间处理大约7,000,000个事务。
By relating these tasks to the Server task, you can understand how the CPU resources are being consumed by the various tasks that make up this DPAR.
通过将这些任务与Server任务关联，可以理解CPU资源如何由组成该DPAR的各种任务消耗。
The Server task was chosen for this example because this DPAR is supporting Notes clients, and all NRPC client requests are handled by the Server task.
在本例中选择server任务是因为该DPAR支持的是Notes客户机，所有NRPC客户机请求都由Server任务处理。
A pilot was set up in which roughly 10 percent of the existing Notes user community was migrated to the new DPAR on the new hardware to validate the sizing.
我们设置了一个试验版本，将大约10%的现有Notes用户社区迁移到新硬件上的新DPAR来验证分级。
We subsequently upgraded this DPAR to beta 3 (January 27, 2005) and beta 4 (April 29, 2005), and upgraded to the Domino 7 Gold candidate build on August 26, 2005.
我们后来将此DPAR升级到beta3（2005 年1 月27 日）和 beta4（2005 年4 月29 日），然后在 2005 年8 月26 日升级到Domino7Goldcandidatebuild。
应用推荐