Check the mysql slow query log (see http://dev.mysql.com/doc/refman/5.1/en/slow-query-log.html)
On Feb 25, 6:59 am, Lukasz Szybalski <[email protected]> wrote: > Hello, > I was wondering if you guys could help me determine what the problem > might be with trac/mysql. We were going smooth up until 110K tickets > in trac. What happens now is that after a while (3h) mysql starts > using 100% of the cpu, while all the other requests are waiting. I > need to determine which query is that? Who's running it, etc? or > whether it is my mysql settings? > > Ideas? > > my.mysql: > > key_buffer = 1600M > max_allowed_packet = 16M > thread_stack = 128K > query_cache_limit = 1M > query_cache_size = 64M > > show status like 'qc%'; > +-------------------------+----------+ > | Variable_name | Value | > +-------------------------+----------+ > | Qcache_free_blocks | 62 | > | Qcache_free_memory | 66876024 | > | Qcache_hits | 45233 | > | Qcache_inserts | 1606 | > | Qcache_lowmem_prunes | 0 | > | Qcache_not_cached | 670 | > | Qcache_queries_in_cache | 159 | > | Qcache_total_blocks | 408 | > +-------------------------+----------+ > 8 rows in set (0.00 sec) > > show variables like 'query%'; > +------------------------------+----------+ > | Variable_name | Value | > +------------------------------+----------+ > | query_alloc_block_size | 8192 | > | query_cache_limit | 1048576 | > | query_cache_min_res_unit | 4096 | > | query_cache_size | 67108864 | > | query_cache_type | ON | > | query_cache_wlock_invalidate | OFF | > | query_prealloc_size | 8192 | > +------------------------------+----------+ > 7 rows in set (0.00 sec) > > What can I do to trouble shoot this problem? > > Thanks, > Lucas -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
