Hi Jan, Have you checked the recommendations in the Support Module? Apart from that, the so called "Full text searches" -- which are not using FTS indexes in MySQL, as you might expect -- are known to generate heavy requests. I have a proposal of creating an article search backend that uses MySQL FTS ready, but no customer yet to back up the implementation. If you - or anyone reading this - is interested, please drop me a line. It's not very difficult or expensive.... would be great if we can realize it. Tuning MySQL is a subject in it's own right; you should probably seek support from seasoned MySQL DBA's. Please note that our customers with the highest volumes of tickets and agents are currently using MySQL as their DBMS of choice. And if you happen to stumble on inefficient queries that can be improved, feel free to report them on bugs.otrs.org. -- Mike On Wed, Jun 1, 2011 at 14:13, wrote:

Hi,

we have two OTRS instances on one server, nothing else is running there.

There are some mysql statistics though, that make me worry:

·         Slow_queries: 96

·         Innodb_buffer_pool_reads: 12

·         Handler_read_rnd: 9,198 k

·         Handler_read_rnd_next: 710 M

·         Created_tmp_disk_tables: 2,581

·         Select_full_join: 31 k

·         Opened_tables: 29 k

·         Table_locks_waited: 11 k

Some of these could be improved by changing settings of innodb_buffer_pool_size, tmp_table_size and max_heap_table_size in my.cnf, but others (Handler_read_rnd, Select_full_join, …) are pointing to bad optimized requests.

Are there any documents about Mysql-performance (and –tweaking) wrt OTRS? (besides http://doc.otrs.org/2.4/en/html/performance-tuning-database.html I mean)

Regards,

Jan Dreyer

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs