Define the performance requirements of hardware and software.
定义硬件和软件的性能需求。
You can define performance requirements on several test elements.
您可以定义一些测试元素的性能需求。
Rigorously distinguish your functional and performance requirements.
严格地区分您的功能和性能要求。
As much as you can, use known solutions to meet reliability and performance requirements.
你应尽量采用那些已知的方案以满足可靠性与性能需求。
We needed to assess the Castor product to make sure it met our system's performance requirements.
我们需要评估Castor产品以确保它能够符合我们的系统性能的要求。
Services still have to be scalable, secure, reliable, and meet necessary performance requirements.
服务必须具有可扩展性、安全性、可靠性，并且符合必要的性能需求。
These applications have varied architectures, and service, availability, and performance requirements.
这些应用具有不同的架构以及在服务、可用性与性能上的不同要求。
Our system didn't have demanding performance requirements, but we wanted it to be usable under peak loads.
我们的系统没有苛刻的性能需求，但是我们想让系统在最大负载下是可用的。
For small applications with low performance requirements, there is no need for formal performance testing.
对于具有低的性能需求的小型应用程序，没有必要进行正式的性能测试。
A simple two tier database-only approach is not likely to achieve the performance requirements outlined above.
一个只有两层的简单数据库方案不太可能达到上述性能需求。
As with any application, thoroughly testing your application ensures Solr meets your performance requirements.
与任何应用程序一样，全面地测试应用程序可确保Solr能够满足您的性能需求。
What if you could specify and validate that these load and performance requirements are being met at least once a day?
如果您每天至少可以指定并确认一次这些负载和性能需求得到了满足，又会怎样？
If applications have high-performance requirements, applications should be designed to process messages sequentially.
如果应用程序具有高性能要求，则应该将应用程序设计为按顺序处理消息。
Managing access to those Shared resources is essential for meeting the high-performance requirements for J2EE applications.
管理对那些共享资源的访问对于满足J2EE应用的高性能需求来说至关重要。
For applications that receive large volumes of queries, a single Solr server may not be enough to meet performance requirements.
对于收到大量查询的应用程序，单一一个Solr服务器恐怕不足以满足性能上的需求。
In this final installment, I'll introduce a transaction strategy that's useful for applications with very high-performance requirements.
在这最后一部分中，我将介绍对于具有高性能需求的应用程序非常有用的事务策略。
Every test case related to the performance requirements essentially describes all inputs to the system as well as all outputs expected from the system.
每个测试用例都是针对性能需求设计的，从根本上描述了系统的所有输入和预计的系统输出。
With Release 8.1, we've added the concept of performance requirements so that you can immediately validate those objectives at the end of your performance test.
有了8.1版本，我们已经添加了性能需求的概念，这样你就可以在性能测试的末期马上验证这些目标。
Normalization focuses only on the meaning of the data, without consideration given to the possible performance requirements of the applications accessing the data.
规范化只关注数据的意义，而没有考虑对于访问数据的应用程序的性能需求。
For example, an application can check WSRR just before invoking a service to locate the service instance best satisfying its functional and performance requirements.
例如，应用程序可以在调用服务前检查WSRR，以查找最能满足其功能和性能需求的服务实例。
Use the information here to ensure that your application USES the appropriate invocation style based on your service endpoints, performance requirements, and so forth.
使用本文的信息可确保应用程序基于服务端点、性能需求等使用相应的调用样式。
This tutorial shows you a simple and effective caching technique, based on a mature product feature, DynaCache, that will help you meet application performance requirements.
本教程将向您展示一种简单有效的缓存技术DynaCache，它基于一个成熟的产品特性，能够帮助您满足应用程序性能需要。
If we treat accessibility requirements as ordinary requirements, then they will appear in developers' task descriptions, together with functional and performance requirements.
如果我们把易访问性需求作为一般的需求，那么它们将和功能与性能需求一起出现在开发人员的任务描述中。
Depending on your performance requirements, you can also mix physical and virtual servers - leaving the higher volume and more performance sensitive applications on physical servers.
根据您具体的性能需求，您还可以混合使用物理的和虚拟的服务器，将高容量的和在性能方面更加敏感的应用程序放在物理服务器上。
One of the reasons for this can be attributed to strict performance requirements for the step (defined in the SLA); the overhead required for a service invocation might be too costly.
这其中的一个原因可归结为步骤的严格性能要求（在SLA 中定义）；服务调用的开销可能会太大。
Among the few with performance requirements that admit parallelization, most I've met simply recite that PHP "doesn't do threads" and resign themselves to their existing computational model.
在具有使用并行实现性能需求的少数人当中，我遇到的大多数人全都说PHP“不支持线程”，并且甘于使用现有的计算模型。
It may be a good option if your application fits the XML Code model and does not have stringent performance requirements, but JBind seems relatively cumbersome for general XML data binding usage.
如果应用程序适合“XML代码”模型，并且对性能的需求也不迫切，则JBind可能是很好的选择，但对于使用一般的XML数据绑定，它显得比较笨拙。
When considering this option you must be careful to ensure that all of the functionality you require is exposed as a Web service, and that the API you chose will meet your performance requirements.
在考虑该选择时，请务必仔细确保所有需要的功能都作为Web服务被公布，并且选择的API可以满足性能要求。
Not Understanding SOA Performance requirements.
缺少对SOA性能需求的理解。
Performance requirements demonstrate the ability to deliver functionality or perform tasks that support a specific policy.
执行要求证明了支持某种特殊政策的交付功能或执行任务的能力。
应用推荐