Conduct initial load and performance tests.
直到初始的负载和性能测试。
This environment is also used for performance tests.
这一环境还可以用于进行性能测试。
Based on performance tests, arrive at a process size.
根据性能测试，得出进程大小。
Increased scalability for large-volume performance tests.
对于大量性能测试的可伸缩性的增长。
Figure 1 illustrates the results of the performance tests.
图1展示了性能测试的结果。
Review these performance tests before you start to create your own.
在您创建它之前就可以评审这些性能测试。
Our performance tests were conducted with a supported remote source.
我们的性能测试是用一个受支持的远程数据源进行的。
Or, performance tests have to be run to determine initial benchmarks.
又或者，必须运行性能测试来确定初始基准。
The Herons have failed to pass a number of performance tests this year.
那一年Herons未能通过很多性能测试。
What are your particular challenges when you run your performance tests?
当您执行性能测试时，详细的难题是什么？
This means that running performance tests often involves scavenging for machines.
这意味着运行性能测试常常要重新配置机器的环境。
VMware performance tests suggest that the overhead is in the 8 to 12 percent range.
VMWare的性能测试指出，系统开销在8 - 12个百分点之间。
workload that we can use for future performance tests in a simulated Notes.net environment.
我们还希望创建一个 Notes.net负载，用于在未来的模拟 Notes.net环境中进行性能测试。
I've devised some performance tests that show that Synth won't slow your UI to a crawl.
我设计了一些性能测试，这些测试表明，Synth不会令您的UI慢如蜗牛。
As in the previous article, two sets of request sequences were used for the performance tests.
正如之前的文章所述，有两组请求序列用于性能测试。
As in the previous articles, two sets of request sequences are used for the performance tests.
如此前文章所述，有两组请求序列用于性能测试。
Note that this is a different system from the one used for performance tests in earlier articles.
注意，它与前面文章的性能测试所使用的系统不一样。
This recent beta is the version I used for my evaluation and performance tests in these articles.
在这些文章中，我用这个最近的beta测试版进行评估和性能测试。
Listing 2 shows the Rampart client configuration used with the performance tests in this article.
清单2显示本文中性能测试中用到的Rampart客户端配置。
This article introduces you to clusters, and then looks at our performance tests of R4.6 clusters.
本文首先介绍集群，然后再查看在R4.6集群上进行的性能测试。
The first article introduces you to clusters, and then looks at our performance tests of R4.6 clusters.
本系列的第一篇文章向您介绍了集群，然后查看了在R 4.6集群上进行的性能测试。
We used PushToTest TestMaker to repurpose the tests as functional tests and load and performance tests.
我们使用了PushToTest的TestMaker来重新调整功能性测试和加载及性能测试。
Conducting Domino server performance tests depends largely on the ability to simulate a realistic user load.
执行Domino服务器性能测试依赖于模拟真实用户负载的能力。
For the performance tests I'll cover in Part 2, I generated code using each of these data binding frameworks.
对于将在第2部分中讨论的性能测试，我用每一种数据绑定框架来生成代码。
When running the baseline test or other performance tests, other work on the system must be carefully controlled.
在运行基准测试或其他性能测试时，必须谨慎地控制系统上的其他工作。
As you'll see in this article, our performance tests of Domino R4.6 clusters involved various system configurations.
在本文章您将看到，在DominoR 4.6上进行的性能测试涉及到各种系统配置。
Thus, it is important that response time goals and actual latency times be defined and validated via performance tests.
因此，重要的是要通过性能测试来定义和检验响应时间目标和实际延迟时间。
In addition, performance tests are designed to generate as little overhead as possible, so as not to skew test results.
另外，性能测试被设计成生成尽可能少的负荷，所以并不会产生冗繁的结果。
In addition, performance tests are designed to generate as little overhead as possible, so as not to skew test results.
另外，性能测试被设计成生成尽可能少的负荷，所以并不会产生冗繁的结果。
应用推荐