Static solution for large website pages-php Tutorial

If the pv of a website is too high, a feasible static webpage solution is required. the general functional requirements are as follows: 1. improving the website performance; 2. generating and expiring static pages; 3. convenient management; 4: static file storage problems: 5. some website pages may be modified as the user logs on; 6. unused pages... if the pv of a website is too high, a feasible static webpage solution is required. the general functional requirements are as follows:
1. improve website performance
2: static page generation and expiration mechanisms;
3: Convenient management;
4: static file storage problems,
5. some website pages may be modified as users log on;
6: Use static cache without the beginning and end of the page,
7: It is also convenient to optimize extension later

Reply content:

If the pv of a website is too high, a feasible static webpage solution is required. the general functional requirements are as follows:
1. improve website performance
2: static page generation and expiration mechanisms;
3: Convenient management;
4: static file storage problems,
5. some website pages may be modified as users log on;
6: Use static cache without the beginning and end of the page,
7: It is also convenient to optimize extension later

1. improve website performance
-- In addition to static pages, pay attention to storing static resources such as images, css, and js on CDN.
2: static page generation and expiration mechanisms;
-- Timed generation. use crontab to start a scheduled task. for example, go to automatic page generation in the early morning when the PV is low.
-- The expiration mechanism depends on your specific business needs.
3: Convenient management;
-- How to manage it? Generally, in addition to regular generation, you can create a visual background management system and click it to regenerate the specified page.
4: static file storage problems,
-- Set up NFS and the like. the speed is faster and the fault tolerance is better.
5. some website pages may be modified as users log on;
-- After logging on to the user, JavaScript is used to process the changes.
6: Use static cache without the beginning and end of the page,
-- Generally, this is not required. the whole page has been statically cached. you only need to split the header and footer of the page.
7: It is also convenient to optimize extension later
-- This is too general to answer.