I decided on a Shared memory pool size of 12gb.
我决定共享内存池大小为12gb。
You should also configure pool size based on the and elements.
您还应该根据“InitialCapacity”和“MaxCapacity”元素配置池大小。
Configured maximum pool size displays the configured maximum pool size.
已配置最大连接池大小显示已配置的最大的池的大小。
For other platforms, the buffer pool size is 250 pages with a 4k pagesize.
而在其他平台上，缓冲池大小为250个页大小为4k的页。
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。
To determine whether the BUFFPAGE parameter is in use for buffer pool size of database, run.
要确定数据库的缓冲池大小是否由BUFFPAGE参数所决定，请运行。
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.
另一个极大影响性能的配置参数是数据库缓冲池大小。
Although you can map the pool size extensions, the application servers treat the free pool differently.
虽然您可以映射池大小范围，但是应用程序服务器看待空闲池的方式是不同的。
Now, that you map this pool size with a minimum of 1 and a maximum of 5 to WebSphere Application Server.
现在，您已将最小为1，最大为5的池大小映射到WebSphere Application Server。
On the other hand, if your minimum pool size is too large, you may have allocated unnecessary connections.
相反，如果最小池大小太大，又会分配不需要的连接。
Remember that the servlet engines thread pool size directly affects the MaxClient setting on the Web servers.
别忘了servlet引擎线程池的大小直接影响Web服务器上的MaxClient设置。
The memory pool size and the Max activity level values for the memory pool where QZDASOINIT jobs are running.
内存池的大小和QZDASOINI任务所在内存池的最大活动级别。
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 is similar to creating a fixed-size pool of one, but without being able to change the underlying pool size.
这类似于创建一个固定大小的线程池，但是固定大小的线程池无法更改大小。
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 mapping works fine, in that it does limit the pool size to 5, but it doesn't limit that number of active instances to 5.
这种映射能够工作得很好，因为它的确将池大小限制在5 之内，同时又没有将活动实例的数目限制为 5。
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.
如果应用程序有高并发，而最大池大小又太小，连接池就会经常等待。
When NPAGES has value of -1, the buffer pool size is determined by the BUFFPAGE parameter in the database configuration. For example.
当NPAGES的值为-1时，缓冲池大小就是由数据库配置中的BUFFPAGE参数确定的。
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.
如果对象池大小没有正确调优，许多未使用的对象实例最终会被闲置，耗尽内存而不产生任何价值。
应用推荐