Hi all,
below is a snippet of database analyzer output which seems to indicate that there are some statements that cause the cache to be thrashed and therefore impact overall performance.
Is there any easy way to check on the database level which SQL statements are executed with bad selectivity or do I really have to capture statements on the application level and the run them manually to check performance?
Any hints are appreciated ...
Thanks, Heiko
------------------------------------------------------------------------
===== #149 at 2004-06-04 11:50:23
* W3 Data cache hitrate (SQL Pages) 87.77%, 11108 of 90818 accesses failed
CON: DC_Hit < 96 && ( PReads ) > MAX_IDLE_IO_ALL_DEVS
VAL: 87.77 < 96 && ( 11108 ) > 600
* W3 Selects and fetches selectivity 0.00%: 92 selects and fetches, 1574495 rows read, 3 rows qualified
CON: SelFetSel < 0.3
VAL: 0.00 < 0.3
------------------------------------------------------------------ This mail has been inspected by Webwasher - a CyberGuard Company - leading technology for E-mail and Web Security.
Webwasher - keeping your Web clean! ------------------------------------------------------------------
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
