Are you using Perl DBD-ODBC? If you are, then please look at my other post today; we saw a drop in catalog cache hit rate (from over 92% to 61%) when using cached connections with DBD-ODBC 0.42 and higher.
Jeroen Boomgaardt On Monday, February 17, 2003 at 10:57:42, john wrote: > Can you give me more information regarding how application design can > affect the catalog cache hit rate? I see others achieving rates close to > 100% > > In a small test, I can confirm there are no rollbacks occuring. There are > mostly SELECTS and minor updates. > > What other aspects will play a role in the catalog cache hit rate? > > Thanks > >>From: "Anhaus, Thomas" <[EMAIL PROTECTED]> >>To: [EMAIL PROTECTED] >>CC: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >>Subject: RE:Catalog Cache hit rate, how to increase? >>Date: Mon, 17 Feb 2003 11:17:17 +0100 >> >>John Doed wrote : >> >> >From the DBM GUI I see my Data Cache is 99%-100% but my Catalog hit rate >>is >> >anywhere between 70%-85%. I tried increasing CAT_CACHE_SUPPLY >>significantly >> >but that actually lowered the hit rate average to the mid 70's (it was >>low >> >80's before). >> >> >How do I get Catalog Cache hit rate to 100%? >> >>It is not always possible to increase the catalog hit rate, >>because some events require to empty the cache completely. >>One of this events is a transaction rollback, others are DDL statements >>executed in your session. >>If increasing the parameter CAT_CACHE_SUPPLY does not improve your hit >>rate, >>it seems that it's caused by your application profile. >> >>Regards, >>Thomas _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
