Hello, you should tell us what you do (i.e. what kinds of statements are executed, and what expectations about index use you have).
You should keep an eye on statements that return/affect a large number of records - there is little the database can do if a statement affects 99% of some 1-million-entry table, and for instances all these rows need to be locked. Regards Alexander Schröder SAP DB, SAP Labs Berlin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 15. September 2005 10:08 To: maxdb@lists.mysql.com Subject: Performance Issues (Table Locks, no Index Scans) Hello, We're having performance problems with SAP DB 7.4.3 Build 032-121-068-842 on SuSe Linux 9.0 with kernel 2.6.8-24-default. We tested it on different systems and with different Versions (also tried MaxDB 7.6.012, but no luck). I'm facing a high number of table locks, increasing the MAXLOCKS from 3000 to 10000 or 30000 didn't improve the situation. What can be done to prevent table locks from happening? There also seems to be a problem with the indexes. The Database Manager says there are no Index Scans in that database, but many table scans. Since there are some big tables (+1 Million entries) this worries me. Any comments on tweaking some parameters or other help is very appreciated -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
