可伸缩性是一个主要问题。
可测量性以及性能。
Mail rule scalability improvements.
邮件规则可伸缩性改善。
Load, performance, or scalability.
负载，性能或者评价性。
Design for performance and scalability.
面向性能和可扩展性的设计。
JFS2 file system check scalability.
JFS2文件系统检查灵活性。
Insufficient capacity or scalability plan.
不充足的容量或可伸缩性计划。
The problem is scalability of this process.
问题在于这个过程没有可伸缩性。
Code design for performance and scalability.
性能和可扩展性代码设计。
More performance and scalability improvements.
性能和可伸缩性的更多提高。
Performance, scalability and high availability.
性能，可测量性以及高实用性。
See Code design for performance and scalability.
请参阅性能和可伸缩性代码设计。
可伸缩性。
Easy scalability to multi-petabyte capacity.
可轻松扩展到数PB容量。
In this context, planning for scalability is vital.
在此环境中，可伸缩性方面的规划非常重要！
As we know from technology, scalability is hard work.
从技术角度看，可伸缩性是一个难题。
Scalability is a very distinct concept from capacity.
可伸缩性和能力是非常不同的两个概念。
You must build in scalability to your viral model.
你的病毒模式必须植入可升级性。
Server scalability and performance was another major issue.
服务器的可伸缩性和性能是另一个重要问题。
However, what if your application requires extreme scalability?
然而，如果应用程序需要极端的可伸缩性，该怎么办？
Parameter types in SOAP present a possible scalability problem.
在SOAP里面的参数类型可能呈现一个可扩展性的问题。
Now, it's time to look beyond stability and toward scalability.
现在，我们是时候考虑稳定性之外的可扩展性。
And we'll provide a general rule on post-deployment scalability.
还要提供关于部署后可伸缩性的一般规则。
If it’s a straight line, that’s quite good: “linear scalability”.
如果它是一条直线，那就是非常好的“线性伸缩性”。
More about the work to improve TFS scalability here and here.
从这-里可以看到更多关于改进TFS可测量性的工作。
Server scalability: there is no such thing as “data push” in HTTP.
服务器的可伸缩性：HTTP中并没有所谓的“数据推送”。
A scenario was devised to test the scalability of the application.
为此设计一个情景来测试应用的扩展性。
A high degree of contention is bad for both latency and scalability.
严重的争用对等待时间和可伸缩性都不利。
That was their entire approach to scalability and performance testing.
那是他们进行可伸缩性和性能测试的全部方法。
However, they all suffer from the same problem: they lack scalability.
然而，这些解决方案都遭遇了相同的问题：缺乏可伸缩性。
应用推荐