0
MySQL Conference Liveblogging: The Future Of MySQL (Tuesday 11:55AM)
Posted by Artem Russakovskii on April 15th, 2008 in Databases
- Robin Schumacher
- gives overview of MySQL products
- MySQL Enterprise
- MySQL 5.1 announced
- table/index partitioning -> great for data warehouses, range, cache, key, list, composite, subpartitioning. Partition pruning. Response time greatly improved with proper partitioning.
- row-based/hybrid replication -> safer and smarter
- disk-based cluster -> supports bigger DBs
- built-in job scheduler -> simplified task management
- problem SQL identification -> easier troubleshooting. Dynamic query tracing is now available, no need to trace things in slow query logs.
- faster full-text search -> 500% increase in some cases
- 5.1.24RC available for the conference
- MySQL 6.0
- Falcon engine – transactional engine
- new backup (version 1.0) -> cross engine, non-blocking, to replace mysqldump
- Falcon
- planned default transactional storage engine. Q4 GA (general availability).
- not InnoDB replacement
- most InnoDB apps are OK on Falcon
- crash recovery
- ACID transactions
- more features
- best on multi-CPU, large RAM servers
- planned to beat InnoDB
- shows latest internal Falcon vs InnoDB benchmarks, all benchmarks have Falcon winning now (dual and quad quadcore CPUs), compared to before
- new backup in 6.0
- all general engines supported (except for Cluster)
- SQL-command driven
- online, non-blocking DML (insert,update,delete) for transactional engines. MyISAM is still blocking (at least for now)
- point-in-time recovery
- better recovery times in benchmarks
- restore is blocking
- plugins for the backup tool
- first one is a non-blocking MyISAM plugin
- compression plugin
- encryption plugin
- new optimizer enhancements in 6.0
- example shows 99.75% improvement, seems like a very edgy edge case
- High Availability
- MySQL 5.1 with disk-based cluster and replication for cluster
- Data Warehousing
- MySQL 5.1 with data partitioning
- data management becomes easy if one needs to delete many rows and they sit on one (smartly created) partition. Then a quick DROP DDL statement takes care of the job in a split second.
- better subquery optimizations (6.0)
- New Nitro engine available in 5.1 for real-time data warehousing
- InfoBright engine for TB-sized data warehousing
- Kickfire
- MySQL 5.1 with data partitioning
- memcached
- MySQL Enterprise is going to start offering support
- MySQL Workbench
- use it
- reverse engineer a schema
- find differences
- sync
- free and paid version (nicer functionality in paid only?)
- 2008 plans are shown
- MySQL 6.0, Falcon GA in Q4
- Maria in Q4
- MySQL 6.x
- foreign keys in all storage engines
- better prepared statements
- better server-side cursors -> faster, less memory
- replication improvements -> checksums
- optimizer enhancements
- more
- MySQL 7.0?
- Infobright storage engine
- no indexes needed (wow, definitely need to research this)
- Kickfire
- Rob Young takes over
- talks about Enterprise plans, customer reported pains, a lot have to do with replication
- MySQL Load Balancer (Q3-Q4 2008)
- for high traffic, read intensive apps and websites
- application load balancing extension (not replacement)
- MySQL Enterprise Monitor
- needle in a haystack diagnosis
- MySQL Query Analyzer
- will be able to talk to the Enterprise Monitor
- MySQL Connection Manager (2009)
- connection pooler
- connection concentrator
- optimizes throughput of web applications
- multiplexing transactions onto a single connection
- Lunch time
In the meantime, if you found this article useful, feel free to buy me a cup of coffee below.