We are happy to see that Percona Server/XtraDB and XtraBackup are raising popularity and to keep excitement we want to have more features and more performance fixes! If you are experienced software engineer and feel strong enough to hack InnoDB/XtraDB code we invite you to join our development team to work on the following (but not limited to) problems:
- Fix InnoDB flushing problems, e.g: https://www.percona.com/blog/2011/09/18/disaster-mysql-5-5-flushing/
- Fix InnoDB index locking
- Figure out InnoDB adaptive locking issue, e.g: https://www.percona.com/blog/2010/02/25/index-lock-and-adaptive-search-next-two-biggest-innodb-problems/
- Make some InnoDB tables non-transactional 🙂
- Make InnoDB page size setting per tables and per index
- Specify location of InnoDB tables (e.g: disk or SSD)
- Make InnoDB just in general faster on SSD, so we do need to create several instances, like in my recent benchmarks
- Add more features for Percona XtraBackup
- And work on our new area of interest: clustering solution based on XtraDB + Galera
If any of that sounds interesting, please contact us or drop me email directly.
About the Author
Vadim TkachenkoVadim Tkachenko co-founded Percona in 2006 and serves as its Chief Technology Officer. Vadim leads Percona Labs, which focuses on technology research and performance evaluations of Percona’s and third-party products. Vadim’s expertise in LAMP performance and multi-threaded programming help optimize MySQL and InnoDB internals to take full advantage of modern hardware. He also co-authored the book High Performance MySQL: Optimization, Backups, and Replication 3rd Edition.
Sounds interesting. I’d love to participate. Is it required to be an employee of Percona to be on the development team?
Derek,
We are looking for employment, but I am open to talk on other possibilities.
Please contact me to vadim@ to discuss.
Make some InnoDB tables non-transactional :
ALTER TABLE tablename ENGINE=MyISAM;
done!