>because I need legislative authorization here to stop and restart my TSM
server.
Geesh, and I thought that politics around my shop were bad!
"Brian L. Nick"
<BRIAN. To: [EMAIL PROTECTED]
NICK@PHOENIXWM. cc:
COM> Subject: Re: cache hit rate
Sent by: "ADSM:
Dist Stor
Manager" <ADSM-
[EMAIL PROTECTED]>
08/22/2002 06:25
AM
Please respond to
"ADSM: Dist Stor
Manager"
John,
We were running into performance issues after upgrading the STM server to
4.2.1.15 and Tivoli suggested that bufpoolsize for us. I thought that it
was too large as well. What we were not doing, and still are not, is coding
a region parameter of 512M. We are using the old 0M parameter. I can't
change that right now because I need legislative authorization here to stop
and restart my TSM server. Looks like I'm stuck with the 0M region until
Saturday.
"John Naylor"
<john.naylor@SCOTTISH-SOUT To: ADSM-
[EMAIL PROTECTED]
HERN.CO.UK> cc:
Sent by: "ADSM: Dist Stor Subject: Re:
cache hit rate
Manager"
<[EMAIL PROTECTED]>
08/22/02 05:29 AM
Please respond to "ADSM:
Dist Stor Manager"
I have almost the same as you
os390 2.10 and tsm database 18.5 gb used
I have region size at 512 m but my bufferpool is only 49152
I am seeing 98% plus cache hit, so I do not see where bufpoolsize 225280
is coming from.
"Brian L. Nick" <[EMAIL PROTECTED]> on 08/21/2002 05:34:34 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: John Naylor/HAV/SSE)
Subject: Re: cache hit rate
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************
We are working with Tivoli/IBM right now on an unrelated problem and they
have indicated to us that our cache hit should be above 98%. We are in the
process of making changes to our region size to attempt to address this.
TSM server running on OS/390 2.10 db 37.8Gb 50% utilized. One thing that we
are being told is that a region of '0M' is not a good fit for TSM on this
platform. we are going to be testing region ' 512M ' bufpoolsize 225280.
Our current cache hit % is 97.69.
Brian
Brian L. Nick
Systems Technician - Storage Solutions
The Phoenix Companies Inc.
100 Bright Meadow Blvd
Enfield CT. 06082-1900
E-MAIL: [EMAIL PROTECTED]
PHONE: (860)403-2281
"KEN HORACEK"
<KHORACEK@INCSYS To:
[EMAIL PROTECTED]
TEM.COM> cc:
Sent by: "ADSM: Subject: Re: cache hit rate
Dist Stor
Manager"
<[EMAIL PROTECTED]
T.EDU>
08/21/02 12:18
PM
Please respond
to "ADSM: Dist
Stor Manager"
No experience. I fact I'm learning from your experience. While you say
"from my training at IBM that a cache hit rate of 99% and above is
recommended"
I found the following statement in the web interface.
The server database performs best with a cache hit ratio above 97% in the
database bufferpool. To tune the bufferpool size, (a) reset the bufferpool
statistics, (b) execute server operations that use the database, and (c)
view the database details to see if the cache hit ratio is above 97%. If
the cache hit ration is NOT above this percentage, increase the size of the
BUFPOOLSIZE specification in the server options file.
Conflicting advice? Perhaps your 97.7% is good and no problem exists.
Let's hear from others. Please......
Ken
[EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 08/21/2002 12:46:04 AM >>>
Hi all,
first I've to thank all participants for the amount of answers I got on my
latest questions. Now I've got a new one which relates on the
bufferpoolsize and the cache hit rate on OS/390 TSM-Servers.
we use the following bufpoolsize: 32768
our chache hit rate: 97,7 %
I know from my training at IBM that a cache hit rate of 99 % and above is
recommended. Is it possible, that a lower cache hit rate can cause
performance-problems? What is your experience?
MfG
Sascha Bräuning
Sparkassen Informatik, Fellbach
OrgEinheit: 6322
Wilhelm-Pfitzer Str. 1
70736 Fellbach
Telefon: (0711) 5722-2144
Telefax: (0711) 5722-1630
Mailadr.: [EMAIL PROTECTED]