A simulation was run with 1000 requests, using the same resource pool size.
使用1000个请求再次运行了一次模拟，使用了相同的资源池规模。
Processor utilization is not the only consideration in tuning the thread pool size.
处理器利用率不是调整线程池大小过程中的唯一考虑事项。
At present, the maximum pool size per process for this allocator is limited to 512mb.
目前，对于这个分配器，每个进程的最大池大小限制为512MB。
One symptom of insufficient concurrency and insufficient connection pool size is an idle CPU.
并发性不足和连接池大小不足的一个症状是CPU闲置。
We recommend you keep increasing the buffer pool size until you see diminishing improvements.
我们建议您不断增加缓冲池大小，直到看到不再有性能提高。
What happens if you increase the buffer pool size to 20,000 4K pages and run PERFORMER again?
如果将缓冲池大小增加到 20,000 个4K页面并重新运行 PERFORMER，那将会发生什么情况呢？
Never have a maximum connection pool size that is greater than the servlet engine thread count.
绝不要使最大的连接池大小大于servlet引擎线程的数量。
Typically, this should be no more than 20-25% greater than the thread pool size in the Web container.
通常，这所增加的大小不应超过web容器中线程池大小的20—25%。
Another configuration parameter that dramatically affects performance is the database buffer pool size.
另一个极大影响性能的配置参数是数据库缓冲池大小。
On the other hand, if your minimum pool size is too large, you may have allocated unnecessary connections.
相反，如果最小池大小太大，又会分配不需要的连接。
(buffer pool size in the db2exfmt output is discussed further in the buffer pool size section below.).
db 2 exfmt输出中的缓冲池大小将在下面的缓冲池大小一节中进行进一步的讨论。
Remember that the servlet engines thread pool size directly affects the MaxClient setting on the Web servers.
别忘了servlet引擎线程池的大小直接影响Web服务器上的MaxClient设置。
If the working set of both LPARs remains less than or equal to the pool size, then the there is no over-commit.
如果这两个LPAR的工作集总和小于或等于池的大小，那么不会发生过量使用。
This makes it easier to update and report the buffer pool size along with other DB2 database configuration parameters.
这使得更新和报告缓冲池大小以及其它DB 2数据库配置参数变得更加方便。
With the buffer pool size of 250 pages, the application test run experienced very poor buffer pool hit ratio of 48.69%.
通过250个页面的缓冲池大小，应用程序测试运行呈现了48.69%的糟糕的缓冲池命中率。
To tune the thread pool size effectively, you need to understand the tasks that are being queued and what they are doing.
要有效地调整线程池大小，您需要理解正在排队的任务以及它们正在做什么。
The figures that follow show the effect of buffer pool size when the amount of concurrency was increased with smaller databases.
下图演示当小型数据库的并发性上升时，缓冲池的大小产生的影响。
If your application has high concurrency and your maximum pool size is too small, your connection pool will often experience waiting.
如果应用程序有高并发，而最大池大小又太小，连接池就会经常等待。
Our second hypothesis was that specifying the buffer pool size affects memory utilization differently at various user loads (Test Case #2).
我们的第二个假设是指定缓冲池大小对内存利用率的影响因用户负载不同而不同（测试案例 #2）。
If the pool size is not tuned correctly, many unused object instances can end up hanging around, using up memory without contributing value.
如果对象池大小没有正确调优，许多未使用的对象实例最终会被闲置，耗尽内存而不产生任何价值。
The pool size (orange) is the average number of threads in the pool, and the active count (red) is the number of concurrently active threads.
池大小(黄色)是池中线程数量的平均值，而活动计数(红色)是当前活动线程的数量。
This setting was only expected to be needed in a test environment, but if the pool size limit maximum is reached, an error message appears.
这个设置只需要在测试环境中进行，但是如果达到了池的最大限额，将会出现一个错误消息。
With WebSphere Application Server v4.0 and later, the thread pool defines minimum and maximum sizes which reflect the limits of the pool size.
在WebSphereApplicationServerV4.0和更新的版本中，线程池定义了反映池大小的限制的最小值和最大值。
After making sure that you can use the BUFFPAGE parameter in the database configuration to control the buffer pool size, set it to a proper value.
确保可以使用数据库配置中的BUFFPAGE参数来控制缓冲池大小之后，将该参数设置成合适的值。
We can see from the figures that there appears to be a significant benefit to managing the buffer pool size when there's a high degree of concurrency.
从这些图可以看到，当并发性程度很高时，管理缓冲池的大小能够获得显著的性能提升。
These fields provide a big picture for monitoring production load and analyzing pool usage so you can define the optimum value for your maximum pool size.
这些字段为监视生产负载和分析池使用情况提供了一个总体概貌，有助于您为最大池大小定义一个最佳值。
If each buffer pool has an NPAGES value of -1, then the buffer pool size is being controlled through the BUFFPAGE parameter in the database configuration.
如果每个缓冲池都有一个为“-1”的npages值，那么缓冲池大小是由数据库配置中的BUFFPAGE参数控制的。
If the working sets become slightly larger than the pool size, then some paging will occur as the Hypervisor rebalances the memory usage across the LPARs.
如果工作集略微大于池大小，那么在Hypervisor跨lpar重新平衡内存使用量时，会发生一些分页操作。
This is important information for you, as an administrator, because you control the buffer pool size specification and you can decide what size to specify.
这些信息对您很重要，因为作为一名管理员，您要控制缓冲池大小规格和决定要指定的缓冲池大小。
In fact, depending on the type of SQL performed by your application, increasing the buffer pool size over a certain limit may not improve performance any further.
实际上，取决于应用程序所执行的SQL的类型，将缓冲池的大小增加到某个极限之后就可能不会再提高性能了。
应用推荐