MySQL 5.4 is based on MySQL 5.1 but includes small, high-impact changes to enhance scalability and performance in MySQL Server. The following list summarizes MySQL 5.4 areas of emphasis. Section 1.4.2, “MySQL 5.4 Feature Summary”, provides additional detail.
Scalability improvements.
The principal emphasis is to improve scalability on
multi-core CPUs. The trend in hardware development now is
toward more cores rather than continued increases in CPU
clock speeds, which renders “wait until CPUs get
faster” a nonviable means of improving database
performance. Instead, it is necessary to make better use
of multiple cores to maximally exploit the processing
cycles they make available. MySQL 5.4 takes
advantage of features of SMP systems and tries to
eliminate bottlenecks in MySQL architecture that hinder
full use of multiple cores. The focus has been on
InnoDB, especially locking
and memory management.
InnoDB I/O Subsystem changes.
InnoDB I/O subsystem changes
enable more effective use of available I/O capacity.
Enhanced Solaris support. Several modifications improve operation of MySQL Server on Solaris.
Diagnostic and monitoring capabilities.
There is better access to execution and performance
information. Diagnostic improvements include DTrace
probes, expanded
SHOW ENGINE
INNODB STATUS output, and a new status variable.
Configuration changes. The “out of box” configuration provides better choices of default option and system variable values for MySQL operation on up to 16-way x86 servers and 64-way CMT servers with 4GB or more memory.
The following constructs are deprecated and will be removed in a future MySQL release. Where alternatives are shown, applications should be updated to use them.
The table_type system
variable (use
storage_engine).
The TYPE table option to specify the
storage engine for CREATE
TABLE or ALTER
TABLE (use ENGINE).
The SHOW TABLE TYPES SQL statement (use
SHOW ENGINES).
The log_bin_trust_routine_creators
variable (use
log_bin_trust_function_creators).
TIMESTAMP(:
The ability to specify a display width of
N)N (use without
N).
The SHOW INNODB STATUS and
SHOW MUTEX STATUS SQL statements (use
SHOW ENGINE
INNODB STATUS for both of these).
The LOAD TABLE ... FROM MASTER and
LOAD DATA FROM MASTER SQL statements.
The SHOW PLUGIN SQL statement (use
SHOW PLUGINS).
The BACKUP TABLE and The
RESTORE TABLE SQL statements.
The --master-
server options to set replication parameters (use the
xxxCHANGE MASTER TO statement
instead): --master-host,
--master-user, --master-password
, --master-port,
--master-connect-retry,
--master-ssl,
--master-ssl-ca,
--master-ssl-capath,
--master-ssl-cert,
--master-ssl-cipher,
--master-ssl-key.


User Comments
Add your own comment.