Statistics on the differences between Percona Server 5.6 and 5.5

Source: Internet
Author: User
Tags percona percona server

Statistics on the differences between Percona Server 5.6 and 5.5

I. Discard:
1. SHOW [GLOBAL] temporary tables is disabled. Only TEMPORARY_TABLES and GLOBAL_TEMPORARY_TABLES can be used.
2. The innodb_thread_concurrency_timer_based parameter is canceled. The default value 5.5 is false. innodb is enabled to control thread concurrency.
The lockless timer mechanism will be used. The original mutex mechanism is used by default.
3. The innodb_recovery_stats parameter is abolished: the detailed process of record recovery is included in errorlog.
4. The rows_read columns in the slow query log and show processlist are no longer displayed, because they are fuzzy values and do not make much sense.

Ii. Substitution:
1. The output part of the oldest view of show engine innodb status is adjusted to the xtradb_read_view display in section 5.6.
2. Adjust the memory part of the hash table of show engine innodb status to XTRADB_INTERNAL_HASH_TABLES.
3. The INNODB_RSEG table is renamed to XTRADB_RSEG.
4. Different implementation methods are used to allocate a fixed size for the pre-read area: the value of the pre-read area of the cache is calculated only once when each cache pool is initialized,
Instead of hard coding to 64 MB (Previous Version)
5. The response time distribution statistics function is implemented in the form of a plug-in. The original statistics function is extended. Separate statistics are made for read and write, and slow updates of the replication thread are made.
The SQL statement is not counted. The SHOW QUERY_RESPONSE_TIME command is abolished and the query_response_time table is directly queried.
Changed the FLUSH QUERY_RESPONSE_TIME variable to query_response_time_flush control.

3. similar or equivalent functions (the official version is added or percona has made further upgrades ):
1. Crash-Resistant Replication is replaced by MYSQL creash safe replication
2. Improved InnoDB I/O Scalability patch has been Improved (the innodb_adaptive_flushing_method parameter is abolished,
Innodb_checkpoint_age_target, innodb_flush_neighbor_pages, innodb_read_ahead
New: innodb_log_checksum_algorithm)
3. the InnoDB Data Dictionary Size Limit function uses the table-definition-cache variable in 5.6 to Limit the Data Dictionary Size.
4. Expand Table Import is replaced by the InnoDB transportable tablespaces Function
5. The InnoDB data dictionary INFORMATION_SCHEMA tables have been superseded by the MySQL implementations
6. XtraDB SYS_STATS persistent table and index statistics has been replaced by the MySQL 5.6 implementation
7. Dump/Restore of the Buffer Pool is replaced by the official 5.6 Function
8. fast_index_creation (replaced by MySQL 5.6's ALGORITHM = option ).
9. Fast InnoDB Checksum has been deprecated after Percona Server 5.5.28-29.2 because the innodb_checksum_algorithm
Variable in MySQL 5.6 makes it redundant.
10. Handle BLOB End of Line feature has been replaced by MySQL 5.6 binary-mode configuration option.
11. Percona Server 5.5 implemented utf8_general50_ci and ucs2_general50_ci collations as a fix
The upstream bug: #27877. These are now being replaced by MySQL 5.6 utf8_general_mysql500_ci
And ucs2_general_mysql500_ci collations.
12. Percona Server INFORMATION_SCHEMA _ STATS tables in 5.5 have been replaced by new tables in MySQL 5.6:
INNODB_SYS_TABLES, INNODB_SYS_INDEXES, INNODB_SYS_COLUMNS, INNODB_SYS_FIELDS, INNODB_SYS_FOREIGN,
INNODB_SYS_FOREIGN_COLS, INNODB_SYS_TABLESTATS (although MySQL 5.6 does not have MYSQL_HANDLES_OPENED,
Instead it has REF_COUNT). Following tables haven'tbeen implemented in MySQL 5.6 but information is
Available in other tables: INNODB_SYS_STATS-use MYSQL. INNODB _ (INDEX | TABLE) _ STATS instead,
INNODB_TABLE_STATS-use INNODB_SYS_TABLESTATS or MYSQL. INNODB_TABLE_STATS instead,
And INNODB_INDEX_STATS-use MYSQL. INNODB_INDEX_STATS instead.

4. Introduction from 5.5:
Feature Ported Version
Thread Pool v5.6.10-60.2
Atomic write support for Fusion-io devices 5.6.11-60.3.
Improved InnoDB I/O Scalability 5.6.11-60.3
Improved NUMA support 5.6.11-60.3.
Suppress Warning Messages 5.6.11-60.3
Improved MEMORY Storage Engine 5.6.11-60.3
Restricting the number of binlog files 5.6.11-60.3
Too Many ons Warning 5.6.11-60.3
Error Code Compatibility 5.6.11-60.3.
Lock-Free show slave status 5.6.11-60.3.
Percona Toolkit UDFs 5.6.11-60.3.
Support for Fake Changes 5.6.11-60.3
Kill Idle Transactions 5.6.11-60.3
Enforcing Storage Engine 5.6.11-60.3
Utility user 5.6.11-60.3
Extending the secure-file-priv server option 5.6.11-60.3
Expanded Program Option Modifiers 5.6.11-60.3
XtraDB changed page tracking 5.6.11-60.3
PAM Authentication Plugin 5.6.11-60.3
User Statistics 5.6.11-60.3
Slow Query Log 5.6.11-60.3
Extended Show Engine InnoDB Status 5.6.11-60.3
Count InnoDB Deadlocks 5.6.11 to 60.3
Log All Client Commands (syslog) 5.6.11-60.3
Show Storage Engines 5.6.11-60.3
Thread Based Profiling 5.6.11-60.3
Fixed Size for the Read Ahead Area 5.6.13-60.5
Improved Buffer Pool Scalability 5.6.13-60.6
Multiple Adaptive Hash Search Partitions 5.6.13-60.6
HandlerSocket 5.6.17-66.0
Response Time Distribution 5.6.21-69.0

5. Differences between status and variables ....

An example of problem solving in CentOS compiling and installing Percona Server 5.5.42

Percona Server details: click here
Percona Server: click here

This article permanently updates the link address:

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.