June 19, 2013

Post: Why MySQL could be slow with large tables ?

lists or blogs you probably heard complains about MySQL being unable toto several tables or perform complex queries finding relationships between objects. Normalized structure and a lot of joins is right way to

Post: Full Text Search Webinar Questions Followup

to the MySQL queries would make them even slower, I’m sure. Indeed, the result set ofto be coded to search both indexes to find all matches among the most current data.  You would merge

Post: SHOW INNODB STATUS walk through

of previous statements. For complex deadlock investigations you might need to look at the log files to findtable 0 LIST OF TRANSACTIONS FOR EACH SESSION: —TRANSACTION 0 0, not started, process no 3396, OS thread id 1152440672 MySQL

Post: The relationship between Innodb Log checkpointing and dirty Buffer pool pages

of dirty pages get flushed) has a look through the dirty pages in the buffer pool to findhow that algorithm works without reading the source code. There are a lot of ways to tune this, here is a list ofto the same file by more than one thread (particularly if you have relatively few tables