How to optimize the list with massive data and frequent updates

How to optimize the list with massive data and frequent updates? Currently, there are a lot of website data and frequent updates. how can I optimize such a website content list page? At present, we have generated static data and more data, so the time consumed by each generation will be terrible. Does anyone know how the list of those large websites is handled? Begging for a solution ...., it turns out that large websites need to do some big website practices. for example, frequent updates such as follow-up on hardware are not suitable for static massive data and frequently updated lists. how can we optimize this?
Currently, there are a lot of website data and frequent updates. how can I optimize such a website content list page? At present, we have generated static data and more data, so the time consumed by each generation will be terrible. Does anyone know how the list of those large websites is handled? Begging for a solution ....

------ Solution --------------------
It turns out that large websites require some big website practices, such as hardware follow-up.
Frequently updated things are not suitable for static operations. why do frequently updated things need static operations?
If it is about architecture, you have to consider restructuring.

How to optimize the solution by introducing memcache and other methods for sharing data among multiple servers.
Or dynamically read the changed part of the content.
------ Solution --------------------
Due to frequent updates, you only need to replace the last few pages on the list page.
For example, if there are 50 entries on each page, the original 1st page will become 2nd after 50 new entries are added, and the content is the same as the original first page.

In addition, pay attention to the fact that few people flip pages more than 10 times along the pages. More use of the search function
------ Solution --------------------
Frequent updates are not suitable for static scenarios. The last minute was just the next minute, and it was updated again. no...
------ Solution --------------------
Discussion

Frequent updates are not suitable for static scenarios. The last minute was just the next minute, and it was updated again. no...

------ Solution --------------------
Count the locations where multiple people are queried. for example, the first one hundred electronic products can generate static pages for these one hundred websites and use the user search function, this avoids invalid and wasteful operations. if the database is slow to query, data can be divided into tables in addition to optimization such as algorithm statements and indexes. for example, proposing popular electronic products from commodities can relieve some of the pressure. The Big Website architecture is the core.
------ Solution --------------------
It depends on the frequency of frequent updates. The cache technology is required. There are many methods, and the architecture may need to be re-designed...
Once large-volume and high-concurrency data is involved, you need to constantly follow up on the hardware. there is no actual environment, and you can only give it a general reference ..
------ Solution --------------------
Discussion

It depends on the frequency of frequent updates. The cache technology is required. There are many methods, and the architecture may need to be re-designed...
Once large-volume and high-concurrency data is involved, you need to constantly follow up on the hardware. there is no actual environment, and you can only give it a general reference ..

------ Solution --------------------
I came in to learn

Can't I change the database?
------ Solution --------------------
You have to learn this.
------ Solution --------------------
Discussion

Reference:

Due to frequent updates, you only need to replace the last few pages on the list page.
For example, if there are 50 entries on each page, the original 1st page will become 2nd after 50 new entries are added, and the content is the same as the original first page.

In addition, pay attention to the fact that few people flip pages more than 10 times along the pages. More use of the search function

Update hundreds of images every day. as you said, the subsequent pages are dynamic?

------ Solution --------------------
Discussion

Reference:

Due to frequent updates, you only need to replace the last few pages on the list page.
For example, if there are 50 entries on each page, the original 1st page will become 2nd after 50 new entries are added, and the content is the same as the original first page.

In addition, pay attention to the fact that few people flip pages more than 10 times along the pages. More use of the search function

Update hundreds of images every day. as you said, the subsequent pages are dynamic?

------ Solution --------------------
Static is not omnipotent ...... It should not be static at all. different cache measures can be used in key areas.

In order to reduce the pressure, this measure has actually become a pressure. isn't it funny?
------ Solution --------------------
You can use a single volume to generate static data by using a single volume that is triggered by a single volume of requests. the advantage of this is that a single page update is generated in the background, for infrequently accessed pages, resources are not wasted due to frequent unnecessary generation. frequently accessed pages are frequently updated and generated. The principle is:
If a page was generated at last time and accessed by a user at, you only need to call js to trigger the page again, when the next visitor visits, the page is actually Updated at, so that only one page is updated each time, and it will not take too long, in addition, the background generation triggered by js does not affect front-end access.
If you are worried about frequent updates by too many visitors, you can use php to obtain the last update time of the page to be updated. if the update time is less than half an hour earlier than the current time, ignore the update, if it takes more than half an hour, you can generate a new static page.

A large portal website I used to perform automatic updates in this way. it does not need to be manually generated in the background. it not only wastes manpower, but also has a great effect.
------ Solution --------------------
Discussion

Static is not omnipotent ...... It should not be static at all. different cache measures can be used in key areas.

In order to reduce the pressure, this measure has actually become a pressure. isn't it funny?

------ Solution --------------------
Scheduled service, automatic page generation, and push
------ Solution --------------------
Discussion
Reference:

Frequent updates are not suitable for static scenarios. The last minute was just the next minute, and it was updated again. no...

Otherwise!
Suppose there are 100 people accessing each minute
Only one operation is required to generate a static page
100 dynamic operations are required

Besides, the update list page is only made when data is submitted.

------ Solution --------------------