I believe you change the buffer pool size in the dsmserv.opt file and use an
entry as follows:
BUFPOOLSIZE 16384
The accepted way to do this is to note your current buffer pool size and then
double it. Watch your cache hit percentage
for a day or two and then double again to achieve the optimal server performance
with should be attained when the cache
hit percentage is stable and above 99 percent...
George Lesho
Storage/System Admin
AFC Enterprises
Reinhold Wagner <[EMAIL PROTECTED]> on 02/14/2001 10:13:43 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: George Lesho/Partners/AFC)
Fax to:
Subject: Re: Performance Large Files vs. Small Files
After performing the command _q db f=d_ you will see a screen like this:
Available Space (MB): 12,000
Assigned Capacity (MB): 12,000
Maximum Extension (MB): 0
Maximum Reduction (MB): 2,684
Page Size (bytes): 4,096
Total Usable Pages: 3,072,000
Used Pages: 2,377,010
Pct Util: 77.4
Max. Pct Util: 77.6
Physical Volumes: 12
Buffer Pool Pages: 32,768
Total Buffer Requests: 98,257,473
Cache Hit Pct.: 97.76
Cache Wait Pct.: 0.00
Backup in Progress?: No
Type of Backup In Progress:
Incrementals Since Last Full: 0
Changed Since Last Backup (MB): 191.43
Percentage Changed: 2.06
Last Complete Backup Date/Time: 02/14/01 07:01:06
Look at _Cache Hit Pct._ - it should be as high as possible, we were told 98% or
better 99%.
If it's too low you should increase the buffer pool.
Reinhold Wagner, Zeuna Staerker GmbH & Co. KG
