Figure 5 shows an example of an ideal performance test environment.
图5展示里了一个理想的性能测试环境的示例。
In the Performance Call Graph view (Figure 3), the line's thickness indicates the amount of time the application spends along that code path.
在性能调用图视图(图3)中，线的粗细指出应用程序沿着代码路径花费的时间。
As shown in Figure 4, the metadata servers manage portions of the namespace and can overlap (for redundancy and also for performance).
如图4所示，元数据服务器管理名称空间部分，可以(为冗余和性能)进行重叠。
Figure 1 gives a nice graphical representation of overall performance.
图1给出了关于整体性能的图形表示。
With the bigger buffer pool of 12000 4k pages, the performance result improves from 43 completed transactions per 10 seconds to 66 completed transactions, as shown in Figure 4.
通过12000个4K页面的更大缓冲池，性能结果从每10秒完成43个事务增加到完成66个事务，如图4中所示。
Figure 1 shows the performance characteristics of the server as a function of load (simulated users).
图1展示了服务器随负载（模拟用户）而变的性能特征。
Figure 1 below shows this differences between regular disk drives and SSDs in terms of performance.
图1展示了常规硬盘驱动器与SSD之间的性能差异。
Compare it to Figure 2 and you notice that the performance of the knowledge base is already better than that of the first knowledge base you built.
与图2进行比较，您会注意到，知识库的性能已经比第一次构建的知识库好多了。
Figure 3 provides further indication of NIO's performance.
图3进一步显示了NIO的性能。
Notice that the performance of the knowledge base is now better than the performance reported in either Figure 2 or Figure 4.
注意，现在知识库的性能比图2或图4报告的性能更好了。
Figure 3 below, the Performance Investigator example, shows the average disk service time and the average disk wait time for a given period of time.
图3是一个PerformanceInvestigator示例，展示了一个给定时段的平均磁盘服务时间和平均磁盘等待时间。
Figure shows relationship of performance, practices, and capabilities.
图中显示业绩、实践，和能力的关系。
Figure 16. Performance benefit of servlet caching.
图14.servlet缓存的性能改进。
In the Performance schedule wizard, enter the name of the schedule, and then click Finish, as shown in Figure 11.
在PerformanceSchedule向导中，输入调度的名称，然后点击Finish按钮，如图11所示。
By selecting the process performance object in the "Add counters" dialog, a comprehensive list of process level counters are displayed (Figure 5).
通过在“AddCounters”对话框中选择process性能对象，就可以显示进程级计数器的整个清单(图5)。
You see a graph and a table in the right frame of the Performance Viewer, as shown in Figure 12.
您将在PerformanceViewer的右框架中看到一个图形和一个表，如图12所示。
Figure 2: Identifying high-use data can help maximize the performance benefits of SSDS.
图2：挑出高使用率数据有助于将SSD带来的性能好处最大化。
Figure 12 shows an example of a performance profile imported into Microsoft Excel.
图12显示了一个导入到MicrosoftExcel中的性能概况的例子。
One way of maintaining performance at an optimal level is to develop a Web service metrics application (see Figure 8) to measure how well the defense in depths are performing in the orchestra.
将性能保持在最优水平的一个方法是开发一个Web服务度量应用程序(请参见图8)，以测定深度防御的协调程度。
Figure 26 shows the relative performance of the queue and HTTP connector compared with the same Business Events scenario not using a connector.
图26展示了使用队列和HTTP连接器与未使用连接器的BusinessEvents场景的相对性能。
Unfortunately, the view in Figure 3 is obscured by the atrocious performance of String.
不幸的是，图3的视图显示String的性能非常糟糕。
Figure 3 is a screenshot of the JConsole showing data from the Glassbox Inspector monitoring the performance of the Duke's Bookstore sample application (see Resources).
图3是一幅JConsole的截屏，显示了Glassbox Inspector监视duke书店示例应用程序性能的情况。(请参阅参考资料)。
Figure 4 takes String out of the equation and rescales the chart to show more clearly how Rope and StringBuffer performance compare.
图4从比较中撤出 String的结果，调整了图表的比例，更清楚地显示了Rope和StringBuffer性能的对比。
In Figure 11, Rational Quantify compares two data sets and highlights chains of calls where performance has improved (green line) and chains of calls where performance has dropped (red line).
图11中，RationalQuantify比对了两类数据集，并强调了性能改进的调用链(绿线)和性能下降的调用链(红线)。
Figure 3 shows the number of transactions completed with one buffer pool of 250 4k pages: (Note: Performance results may differ on your system.)
图3显示了用一个包含250个4K页面的缓冲池所完成的事务数目：(注意：您系统上的性能结果可能不同。)
Applications that exhibit server affinity can still take advantage of improved communication performance through co-location of WebSphere MQ and BPC on the same physical server, as shown in Figure 2.
具有服务器关联性的应用程序仍然可以通过将WebSphereMQ和BPC安装在相同物理服务器上来改善通信性能，如图2所示。
Details of the tool used for testing (for instance, Rational Performance Tester was used to generate the sample charts in Figure 1 and Figure 2).
用于进行测试的工具的详细信息(例如，使用了RationalPerformance Tester生成图1和图2中的示例图)。
Surprisingly, one of the best performance results came from having the transaction logs held in RAM (see the yellow line in figure 5).
奇怪的是，性能最好的结果来自于在RAM中使用事务记录(见图5中的黄线)。
Figure 1 illustrates the results of the performance tests.
图1展示了性能测试的结果。
Leverage as much data as possible in order to figure out your version of "normal" performance.
利用尽可能多的数据，以了解自己的“正常”表现程度。
应用推荐