Update log:

Add batch file cleaning function on March 26, 2022

Fix a minor editing bug on April 3, 2022

On June 9, 2022, a problem with the image display on the article page was fixed. The image displayed on the article page normally does not need to be updated

On October 10, 2022, the problem that few pictures of the theme picture list are not displayed will be fixed

On October 21, 2022, a small problem occurred in the modification of the article editing page (this update can be ignored if the article is not manually edited)

The final test conclusions of the plug-in are as follows:

One million data seconds without card opening

Three million data is also opened in one second, but slower than one million

Therefore, it is recommended that the number of articles be controlled within 2 million

Plug in principle:

This plug-in will convert the body field in the database Separated into documents. No longer stored in the database. The database only stores frequently called fields

When the user accesses the page or edits the body, the corresponding document is called to display

Automatically archive when a new article is published

For the speed of file indexing, this plug-in will also distribute all articles evenly to 100 folders

This plug-in is not a purely static plug-in. The page is still dynamic and will not change the original url structure

This plug-in can be compatible with most themes, but it is not guaranteed to be compatible with all themes

A website with a large amount of data can save a lot of server resources According to user feedback, tens of thousands of yuan can be saved in server fees (he is a website group, and there are many websites)

Idiotic operation. It can be operated without knowing any technology

For the first time, you need to click manually, and the articles will be automatically optimized in the future

In the background core operation part, there are only two buttons. You just need to click them and do something else. The rest of the optimization work will be done by plug-ins

Three million articles 18.7G data violence test process:

Before optimization:

Optimization principle:

Before optimization, briefly describe the principle of optimization

What is the concept of 18.7G? Let's compare the hard disk to a runway (in fact, it is the same as a runway, or a graph)

So 18.7G means that the head must run at least 18.7G of capacity. If the head runs far, it will be slow.

Then optimization is to separate the infrequently called data, and see the effect of separating the content of the article.

It is still the 3 million articles, but the size has directly changed to 349 M

The database shrinks directly 54.8x , can the query speed be slow?

After optimization

Opening speed after optimization: (It can't be opened before optimization, so there is no comparison chart.)

3 million data text page speed:

3 million data list page speed:

The speed of the 3 million data list page when the server clears the MySQL query cache (in fact, MySQL has query cache, so the speed is faster than this)

User feedback (the number of articles by this user is 280000):

Before optimization:

After optimization: