Incorrect description of MySQL performance tuning and Architecture Design compiled by readers and friends

FromRyam: p26 penultimate line: original article: "excessive coupling between the logic layer and the storage engine Implementation Layer"

From Ryam: p26 penultimate line: original article: "excessive coupling between the logic layer and the storage engine Implementation Layer "-: "excessive decoupling between the logic layer and the storage engine Implementation Layer" p82 row 9th: "In this way, the paging program is omitted for real-time computing before the split "-: "In this way, the paging program is omitted for real-time computing before paging," p118 row 5th: Original:"

From Ryam:

P26
The second to the last row:
Original article: "excessive solution of logical layer and storage engine Implementation Layer"
->: "Excessive decoupling between the logic layer and the storage engine Implementation Layer"

P82
Row 3:
Original article: "In this way, the paging program is omitted for real-time computing before the split"
->: "In this way, the paging program is omitted for real-time computing before paging"

P118
Row 3:
Original article: "If the system requires a limited guarantee"
->: "If the system requires priority assurance"

P123
Row 3:
Original article: "It is not necessarily based on the metadata of the database"
->: "It is not necessarily based on the database metadata"

P85
Last 2nd rows:
Original article: "Then display objects in bottles"
->: "Then assemble and display objects"

P139
Row 3:
Original article: "There will be a lot of recorded pointer information stored in the same Hash value associated"
->: "A large amount of recorded pointer information will be associated with the same Hash value"

P142
Last 6th rows:
Original article: "Of course, it is not appropriate to create an index if any updated field exists"
->: "Of course, it is not suitable for creating indexes because there are no updated fields"

P171
Row 3:
Original article: "But when there are some self-queries or complicated join Operations"
->: "But when there are some subqueries or more complex joins"

Row 3:
Original article: "group_message_bad is the table before optimization and the group_message table after optimization), as shown in the sample code 9-1 :..."

->: Replace group_message with group_message_bad in the sample code.

P194
3rd rows
Original article: "This will not only waste the memory of the Query Cache for frequently changing Table queries"
->: "This not only avoids frequent Table queries from wasting the memory of the Query Cache"

P196
Last 1st rows:
Original article: "first look at the performance configuration items connected to the network and their impact on performance"
->: "Let's take a look at the performance configuration items related to network connections and their impact on performance"

P202
Last 2nd rows:
Original article: "Adjust offline parameters in the Database"
->: "Parameter adjustments made after the database goes online"

P208
Last 6th rows:
Original article: "loading page nodes as well"
->: "Or load the leaf node"

P237
Row 3:
Original article: "We also need to mention the two aspects of system high availability and data security"
->: "You must also mention the high availability and data security of the system"

P246
Row 3:
Original article: "Only when the server-id parameter values of Master and Slave are different"
->: "Only when the server-id parameter values of Master and Slave are inconsistent"

P249
Row 3:
Original article: "The biggest benefit is to avoid the impact of primary Master write operations on the replication of the Slave cluster"
->: "The biggest benefit is to avoid the impact of primary Master write operations on the replication of the Slave cluster"

P261
Last 9th rows:
Original article: "mainly refers to accessing an extremely ordinary table"
->: "Mainly refers to a table with extremely frequent access"

P264
4-3
Original article: "hprizontal sharding"
->: "Horizontal sharding"

Problem: In the horizontal splitting example of the photo albums database, the splitting condition for each split database is album_id % n = 0, which should be album_id % n = 0, album_id % n = 1...

P279
Last 15th rows:
Original article: "When Innodb is in the Local Buffer Pool (...) "
->: "When Innodb is in the Local Buffer Pool (...) "

From cloud:

P153
Original article: "c_rec.group_msg_id = c_rec.id {"
->: "C_rec.group_msg_id = m_rec.id"

FromMysqlkumao
P201
Original article: "10.4.3 Sort Buffer, Join Buffer, and Read Buffer"
->: "10.4.3 Sort Buffer and Join Buffer"

From ochef
Recommendation sequence 2
Original article: "Blog: http://www.orawh.com /"
->: "Blog: http://www.ixdba.com /"

P18
Original article: "such as update, delte, insert, create"
->: "Such as update, delete, insert, and create"

Latest Update: 2009.10.19

From: Jasper Che
P108
Original article: "TL_WRITE_ALLOW_WRITE"
->: "WRITE_ALLOW_WRITE"
Original article: "P108 L7 concurrent Current read lock is the lock type of Read_NO_INSERT"
->: "At the same time, Current read lock is not the lock type of Read_NO_INSERT"

P109
Original article: "Several other storage engines that support transactions"
->: "Other storage engines that support transactions"

P127
Original article: "modifying algorithms only need to access data once"
->: "Only one data access is required to improve the algorithm"
P131
Original article: "mainly including the following centralized types"
->: "Mainly includes the following types"
P148
Original article: "subject LIKE 'weiurazs % '"
->: "AND subject LIKE 'weiurazs % '"

Latest Update: 2009.12.14

Original article address: an incorrect description of MySQL performance tuning and architecture design prepared by readers. Thanks to the original author for sharing this information.