and MySQL Connect is
only 10 days away!
InnoDB is the default storage
engine for Oracle’s MySQL as of MySQL Release 5.5. It provides the standard
ACID-compliant transactions, row-level locking, multiversion concurrency
control, and referential integrity. InnoDB also implements several innovative
technologies to improve its performance and reliability. This presentation
gives a brief history of InnoDB; its main features; and some recent
enhancements for better performance, scalability, and availability.
This session covers performance
tuning with MySQL and the InnoDB storage engine for MySQL and explains the main
improvements made in MySQL Release 5.5 and Release 5.6. Which setting for which
workload? Which value will be better for my system? How can I avoid potential
bottlenecks from the beginning? Do I need a purge thread? Is it true that
InnoDB doesn't need thread concurrency anymore? These and many other questions
are asked by DBAs and developers. Things are changing quickly and constantly,
and there is no “silver bullet.” But understanding the configuration setting’s
impact is already a huge step in performance improvement. Bring your ideas and
problems to share them with others—the discussion is open, just moderated by a
Many top Web properties rely on
Oracle’s MySQL as a critical piece of infrastructure for serving millions of
users. Database availability has become increasingly important. One way to
enhance availability is to give users full access to the database during data
definition language (DDL) operations. The online DDL operations in recent MySQL
releases offer users the flexibility to perform schema changes while having
full access to the database—that is, with minimal delay of operations on a
table and without rebuilding the entire table. These enhancements provide
better responsiveness and availability in busy production environments. This
session covers these improvements in the InnoDB storage engine for MySQL for
online DDL operations such as add index, drop foreign key, and rename column.
demands of Web-based services have generated significant interest in providing
NoSQL access methods to MySQL (MySQL Cluster and the InnoDB storage engine of
MySQL), enabling users to maintain all the advantages of their existing
relational databases while providing blazing-fast performance for simple
queries. Get the best of both worlds: persistence; consistency; rich SQL
queries; high availability; scalability; and simple, flexible APIs and schemas
for agile development. This session describes the memcached connectors and
examines some use cases for how MySQL and memcached fit together in application
architectures. It does the same for the newest MySQL Cluster native connector,
an easy-to-use, fully asynchronous connector for Node.js.
The InnoDB storage engine has
always been highly efficient and includes many unique architectural elements to
ensure high performance and scalability. In MySQL 5.5 and MySQL 5.6, InnoDB
includes many new features that take better advantage of recent advances in
operating systems and hardware platforms than previous releases did. This
session describes unique InnoDB architectural elements for performance, new
features, and how to tune InnoDB to achieve better performance.
compression is an important capability of the InnoDB storage engine for Oracle’s
MySQL. Compressed tables reduce the size of the database on disk, resulting in
fewer reads and writes and better throughput by reducing the I/O workload.
Facebook pushes the limit of InnoDB compression and has made several
enhancements to InnoDB, making this technology ready for online transaction
processing (OLTP). In this session, you will learn the fundamentals of InnoDB
compression. You will also learn the enhancements the Facebook team has made to
improve InnoDB compression, such as reducing compression failures, not logging
compressed page images, and allowing changes of compression level.
Not registered yet? You can still
save US$ 300 over the on-site fee – Register