在查找数据瓶颈时，您应该从中央系统组件开始。
When looking for data bottlenecks, you should start at the central system components.
性能测试的目标就是通过为所有涉及到的组件收集分析数据，识别性能的瓶颈。
The goal of performance testing is to identify the performance bottleneck by collecting analysis data for all components involved.
不幸的是，如果所需数据量远大于内核缓冲区大小的话，这个方法本身可能成为一个性能瓶颈。
Unfortunately, this approach itself can become a performance bottleneck if the size of the data requested is considerably larger than the kernel buffer size.
现在您可以使用该数据来决定每一页面和故障排除潜在瓶颈的百分比。
This data can now be used to determine the percentage of outliers for each page and troubleshoot potential bottlenecks.
在一个信号量保护大量数据时，如果一个或多个任务使用它进行写操作，这个信号量就会成为系统瓶颈。
When a semaphore protects a large amount of data, assuming one or more tasks USES it on a write basis, the semaphore becomes a bottleneck within the system.
更重要的是，如果不观察数据，您如何能确实了解所作的调整是否有助于解除瓶颈？
More importantly, how do you really know if what you've tuned has helped the bottleneck without looking at the data?
在本系列文章的第2部分中，我将会详细地介绍这些变化，使您能够深入地了解aix的各种内存监视工具，以确定瓶颈、以及分析历史趋势和数据。
In Part 2 of this series, I'll discuss these changes in detail as you dive into the memory monitoring tools of AIX to determine bottlenecks and analyze historical trends and data.
如果要写入大量的数据，同时系统没有合理配置的话，审核日志可以很容易地成为该实体系统的瓶颈。
Audit logs can easily become the bottleneck of the entire system if large amounts of data are written and the system is not configured appropriately.
客户端将与数据所在的服务器直接通信，因此，无需使用本身可能成为瓶颈和限制可伸缩性的路由组件。
Clients communicate directly with the servers on which the data is located, so there is no need for a routing component that could itself become a bottleneck and limit scalability.
收集了模拟业务流程所需的所有数据后，您发现了图4中所示的流程瓶颈。
After collecting all the data you need to simulate the business process, you discover the process bottleneck depicted in Figure 4.
除非所搜集的数据清楚地表明CPU是瓶颈，否则并不希望进行CPU优化。
You do not want to tune your CPU unless the data that you've compiled clearly shows that CPU is the bottleneck.
如果你发现中间层正在变成瓶颈，你就必须增加应用服务器的数量，数据层也是同样的状况。
If you see that the middle tier is becoming the bottleneck, you may have to add more no. of application servers and same is the case with the data tier.
批处理瓶颈和冲突数据对订购和配送造成延迟。
Batch bottlenecks and conflicting data delayed orders and shipments.
数据库管理器或数据库配置中的变更是否是产生瓶颈(比如排序溢出)的原因？
Is a change in the database manager or database configuration the reason for a bottleneck, such as a sort overflow?
测试网站仍然遭遇数据库服务器I/O瓶颈，并受数据库服务器磁盘性能的限制。
The test site remains bottlenecked on the database server I/O and bound by performance characteristics of the database server disk.
如果发现用数据库存储的会话是性能瓶颈，而且无法消除它们，那么应该考虑把它们分散到单独的数据库，甚至是多个数据库。
If database back-ed sessions do prove to become a bottleneck for you, and you can't get rid of them, you should be able to split them onto separate databases, or even multiple databases.
这些数据表明网络成为了测试的瓶颈。
Those Numbers might indicate that the tests were bottlenecked by the network.
垂直扩展适用于数据库，但是不足以将数据库作为瓶颈移除，以实现想要的扩展。
Vertical scaling is applied to the database, but is not enough to remove the database as the bottleneck for the type of scaling that you want.
如果某一个磁盘成了瓶颈，那么了解BusinessEvents为什么以及如何持久化数据就变得非常重要，以便对配置进行必要的更改来降低资源争用。
If a particular disk becomes a bottleneck, it's important to understand how and why Business Events persists data so that you can make the necessary configuration changes to reduce contention.
使用这个数据来决定最可能的瓶颈位置，调整系统，并且推断一些特别慢的和经常被使用的servlet或EJB组件，以用于其他的分析以及评测。
Use this data to determine likely bottleneck locations, tune the system, and to understand particularly slow and frequently used servlets or EJB components for additional analysis and profiling.
通过标准（非加速）NICs、FASP有效使用应用程序可用带宽，并移除传统的批量数据传输模式的基本瓶颈。
Using standard (non-accelerated) NICs, FASP efficiently uses the bandwidth available to the application and removes the fundamental bottlenecks of conventional bulk data-transfer schemes.
此分离提供了一些优势，例如最大程度降低了元数据的瓶颈(因为与此服务器交互只需要定位并打开文件)。
This split provides certain advantages, such as minimizing the metadata bottleneck (because interactions with this server are only required to locate and open a file).
是否存在瓶颈(例如公共数据库)？
在其众多的优势中，数据库访问至少存在一个瓶颈：连接。
For all their numerous advantages, database access has at least one bottleneck: connections.
您能够识别并且诊断出性能的瓶颈，无论这种问题是发生在网络、数据库、应用服务器、甚至是用户应用程序之中。
You can identify and diagnose performance bottlenecks, whether such problems occur in the network, database, the application server, or even the user application.
如果您没有足够支持确定瓶颈位置的数据，您就无法改进您的工作过程。
You can’t improve your work processes if you don’t have numbers to support where the bottlenecks lie.
这意味着一个或一些数据库分区承担了更重比例的表行，从而造成了性能瓶颈。
This means that one or some database partitions are assigned a disproportionate number of table rows which can create a performance bottleneck.
这会把理论容量提高到每秒154个请求，瓶颈位置就会转到数据库。
This would give a theoretical capacity of 154 requests per second, pushing the bottleneck to the database.
必须对数据进行分析，以确定业务流程中的瓶颈问题或问题的根源。
The data must be analyzed to identify bottlenecks in the business process, or wherever the cause may lie.
如果查询XML数据源时没有VVM缓存特性，这些因素将会造成很大的性能瓶颈。
These factors can cause considerable performance bottlenecks when querying XML data sources without the VVM caching feature.
应用推荐