Development plans
We are planing to develop next extensions to standard MySQL (in random order, not in order of priority):
-
Integrate google-smp patch or Yasufumi rw-lock patch
-
Integrate Jeremy Cole's extra plugings for having Information Schema for Innodb tables (checking what tables are in memory, what is buffer pool contents etc)
-
Command to check for fragmentation/fill factor for Innodb tables and Indexes
-
Add replication_load statistics. The idea is to measure how much time was passed since replication thread was started (simply need to measure time when it is started) compared to current time. As well as the time
SQL thread spent executing the queries. If we see replication thread was running for 500 seconds and time it spent executing queries is 200 we know replication load is 40% We should just keep it as two numbers so the can be easily incrementally measured (ie each 5 minutes)
-
Query Timeouts
-
Make InnoDB tablespace movable when innodb_file_per_table isused
-
There are two kinds of filesorts. The MSL patch doesn't show which one was chosen for any given query. Also, we could implement a new status variable to count one of the types. This would allow to know the ratio of single-pass filesorts to dual-pass.
-
SHOW MUTEX STATUS not only InnoDB mutexes, but for all (in INFORMATION_SCHEMA)
-
Show pattern access to InnoDB tablespaces
-
create a counter to track the size of the largest implicit temporary table created.
-
Make more of InnoDB's settings into server variables (like page fill factor, LOCK_MAX_DEPTH_IN_DEADLOCK_CHECK, LOCK_MAX_N_STEPS_IN_DEADLOCK_CHECK)
-
Look if can replace standard InnoDB zlib compression to bzip2, lzo, QuickLZ
-
Make InnoDB zlib_compression_level as variable
-
Include the FNV_64() hash function from maatkit into release
-
Add the length of started transaction in PROCESSLIST table so long transaction can be easily caught.
-
Add information about Innodb we have for slow query log in the PROCESSLIST - how long was IO wait so far, how long were row lock waits etc.
-
Add CPU time for the query in PROCESSLIST table.
-
Add query CPU time used in show processlist once we have it.
-
-
Move deadlock output to end of InnoDB status so it does not displace other information
back to Percona Lab page »
