Hello Thomas,
thanks for this first good hint on our cache problem.
After nearly one week of normal operation our catalog cache has raised
to a value of 87%.
This is really better than 70%, but not the value near 99% which should
be optimal.
Perhaps someone can give us some additional hints on catalog cache
settings / tuning.
Best regards
Hannes
--
Hannes Degenhart GPS - Gesellschaft zur Pruefung von Software mbH
Hoervelsinger Weg 54 D - 89081 Ulm - Germany
Pho. +49 731 96657 14 Fax. +49 731 96657 57
mailto:[EMAIL PROTECTED] Web: http://www.gps-ulm.de
Koetter, Thomas Theodor wrote:
Hello Hannes
-----Original Message-----
From: Hannes Degenhart [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 10. August 2005 11:48
To: Maxdb
Subject: Catalog Cache Hit Rate 70% - Cache Settings
[Perl ODBC details]
In the past I've heard something about a "ping" method which
could leed
to bad Catalog Cache hitrates like this.
Yes. The ping-method was implemented with a SQLTables call. I don't know, whether this is
still the case. Better for MaxDB would be a simple "select * from dual". Maybe
you can adjust at your site.
Regards Thomas
----------------------------------------------
Dr. Thomas Kötter
SAP AG, Berlin
NW DT MaxDB
MaxDB: all you need!
www.mysql.com/products/maxdb www.sapdb.org
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
