Paging is often used in our programming. This article will lead everyone to discuss the performance of mysql paging, hoping to help everyone.
Several common paging methods:
1. Escalator method
The escalator method usually only provides two modes of previous page/next page in navigation. Some products do not even provide the previous page function, only provide a "more/more" method, and there are also drop-down automatic loading. More methods can technically be summarized as escalator methods.
The escalator method is relatively simple and efficient in terms of technical implementation. Just get one page further based on the offset of the last item on the current page. Written as SQL it may be similar to
SELECT*FROMLIST_TABLEWHEREid> offset_id LIMIT n;
1. Elevator method
Another data acquisition method is reflected in the product as a precise page turning method, such as 1,2,3...n. At the same time, the user can also input directly to n pages in the navigation. Most scenes in China use elevators, but the technical implementation cost of elevators is relatively high.
In MySQL, the b-tree usually mentioned is usually b+tree in terms of storage engine implementation.
When using the elevator method, when the user specifies to turn to the nth page, there is no direct method to address the location. Instead, it needs to count one by one from the first floor and scan to count*page to obtain the data. It has just started, so the efficiency is not high.
Traditional paging technology (elevator method)
First, the front end needs to pass you the paging entity and query conditions
//分页实体 structFinanceDcPage{ 1:i32 pageSize,//页容量 2:i32 pageIndex,//当前页索引 }
Then you need to return the total number of queries to the front end;
SELECTCOUNT(*)FROMmy_tableWHEREx= y ORDERBYid;
Then return the number of items on the specified page To the front-end:
SELECT*FROMmy_tableWHEREx= y ORDERBYdate_colLIMIT (pageIndex - 1)* pageSize, pageSize;
The results queried from the above two sql statements need to be returned to the front-end paging entity and the single-page result set
//分页实体 structFinanceDcPage{ 1:i32 pageSize,//页容量 2:i32 pageIndex,//当前页索引 3:i32 pageTotal,//总页数 4:i32 totalRecod,//总条数 }
In the traditional query method, only the pageIndex value changes with each request, which is the offset of limit offset, num
For example, limit 0,10; limit 10, 10; …. limit10000,10;
The above changes will cause a deviation in the execution time of each query. The larger the offset value, the longer it takes. For example, limit10000,10 needs to read 10010 pieces of data. Only then can you get the 10 pieces of data you want.
Optimization method
In the traditional method, we learned that the key to efficiency is that the program traverses a lot of unnecessary data and finds the key Click So start here.
If there is no need to use the elevator, we can use the escalator to improve performance.
But in most cases, the elevator form can better meet the needs of users, so we need to find another way to optimize the elevator form.
Optimization based on traditional methods
The optimization methods mentioned above are either difficult to meet the needs of users or too complicated to implement, so If the amount of data is not particularly large, such as millions of pieces of data, there is actually no need to use the above optimization method.
The traditional method is sufficient, but the traditional method may also need optimization. For example:
orderby optimization
SELECT*FROMpa_dc_flowORDERBYsubject_codeDESCLIMIT100000,5
The ORDERBY keyword is used in this statement , then what to sort is very important. If you are sorting auto-incrementing IDs, then this statement does not need to be optimized. If it is an index or even a non-index, then it needs to be optimized.
First of all, you have to make sure it is an index, otherwise it will be really slow. Then if it is an index, but it is not as ordered as an auto-incrementing ID, then it must be rewritten as the following statement.
SELECT*FROMpa_dc_flowINNERJOIN(SELECTidFROMpa_dc_flowORDERBYsubject_codeDESCLIMIT100000,5)ASpa_dc_flow_idUSING(id);
The following is the EXPLAIN for two sql
We can see from the picture that the second sql can scan many fewer pages.
In fact, this involves the optimization issue of order by. The subject_code index is not used in the first sql. If you select subject_code instead... the index is used. The following is the optimization of order by.
order by后的字段,如果要走索引,须与where 条件里的某字段建立复合索引!!或者说orcerby后的字段如果要走索引排序,它要么与where条件里的字段建立复合索引【这里建立复合索引的时候,需要注意复合索引的列顺序为(where字段,order by字段),这样才能满足最左列原则,原因可能是order by字段并能算在where 查询条件中!】,要么它自身要在where条件里被引用到!
表asubject_code为普通字段,上面建有索引,id是自增主键
select*fromaorderbysubject_code//用不上索引 selectidfromaorderbysubject_code//能用上索引 selectsubject_codefromaorderbysubject_code//能用上索引 select*fromawheresubject_code= XX orderbysubject_code//能用上索引
意思是说order by 要避免使用文件系统排序,要么把order by的字段出现在select后,要么使用order by字段出现在where 条件里,要么把order by字段与where条件字段建立复合索引!
第二条sql就是巧妙的利用第二种方式利用上了索引。 select id from a order bysubject_code,这种方式
count优化
当数据量非常大时,其实可以输出总数的大概数据,利用explain语句,他并没有真正去执行sql,而是进行的估算。
相关推荐:
The above is the detailed content of Mysql paging performance exploration. For more information, please follow other related articles on the PHP Chinese website!

InnoDBBufferPool reduces disk I/O by caching data and indexing pages, improving database performance. Its working principle includes: 1. Data reading: Read data from BufferPool; 2. Data writing: After modifying the data, write to BufferPool and refresh it to disk regularly; 3. Cache management: Use the LRU algorithm to manage cache pages; 4. Reading mechanism: Load adjacent data pages in advance. By sizing the BufferPool and using multiple instances, database performance can be optimized.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL is worth learning because it is a powerful open source database management system suitable for data storage, management and analysis. 1) MySQL is a relational database that uses SQL to operate data and is suitable for structured data management. 2) The SQL language is the key to interacting with MySQL and supports CRUD operations. 3) The working principle of MySQL includes client/server architecture, storage engine and query optimizer. 4) Basic usage includes creating databases and tables, and advanced usage involves joining tables using JOIN. 5) Common errors include syntax errors and permission issues, and debugging skills include checking syntax and using EXPLAIN commands. 6) Performance optimization involves the use of indexes, optimization of SQL statements and regular maintenance of databases.

MySQL is suitable for beginners to learn database skills. 1. Install MySQL server and client tools. 2. Understand basic SQL queries, such as SELECT. 3. Master data operations: create tables, insert, update, and delete data. 4. Learn advanced skills: subquery and window functions. 5. Debugging and optimization: Check syntax, use indexes, avoid SELECT*, and use LIMIT.

MySQL efficiently manages structured data through table structure and SQL query, and implements inter-table relationships through foreign keys. 1. Define the data format and type when creating a table. 2. Use foreign keys to establish relationships between tables. 3. Improve performance through indexing and query optimization. 4. Regularly backup and monitor databases to ensure data security and performance optimization.

MySQL is an open source relational database management system that is widely used in Web development. Its key features include: 1. Supports multiple storage engines, such as InnoDB and MyISAM, suitable for different scenarios; 2. Provides master-slave replication functions to facilitate load balancing and data backup; 3. Improve query efficiency through query optimization and index use.

SQL is used to interact with MySQL database to realize data addition, deletion, modification, inspection and database design. 1) SQL performs data operations through SELECT, INSERT, UPDATE, DELETE statements; 2) Use CREATE, ALTER, DROP statements for database design and management; 3) Complex queries and data analysis are implemented through SQL to improve business decision-making efficiency.

The basic operations of MySQL include creating databases, tables, and using SQL to perform CRUD operations on data. 1. Create a database: CREATEDATABASEmy_first_db; 2. Create a table: CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY, titleVARCHAR(100)NOTNULL, authorVARCHAR(100)NOTNULL, published_yearINT); 3. Insert data: INSERTINTObooks(title, author, published_year)VA


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

VSCode Windows 64-bit Download
A free and powerful IDE editor launched by Microsoft

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

SublimeText3 Chinese version
Chinese version, very easy to use