Several caching mechanisms commonly used in PHP_PHP tutorial

Universal caching technology

Data caching: The data caching mentioned here refers to the database query PHP caching mechanism. Every time you access a page, it will first detect whether the corresponding cached data exists. If it does not exist, connect to the database, obtain the data, and sequence the query results. After being transformed and saved to a file, the same query results will be obtained directly from the cache table or file in the future.

The most widely used example is the search function of Discuz, which caches the result ID into a table and searches the cache table first when searching for the same keyword next time.

As a common method, when multiple tables are associated, the contents in the attached table are generated into an array and saved in a field of the main table. When necessary, the array is decomposed. The advantage of this is that only one table can be read, but the disadvantage is that two data Synchronization will take many more steps, and the database is always the bottleneck. Trading the hard disk for speed is the key point in this.

Page cache:

Every time a page is accessed, it will first detect whether the corresponding cached page file exists. If it does not exist, it will connect to the database, get the data, display the page and generate a cached page file at the same time, so that the page file will come into play the next time you visit. . (Template engines and some common PHP caching mechanism classes on the Internet usually have this function)

Time triggered cache:

Check whether the file exists and the timestamp is less than the set expiration time. If the file modification timestamp is greater than the current timestamp minus the expiration timestamp, then use the cache, otherwise update the cache.

Content trigger cache:

Forces the PHP cache mechanism to be updated when data is inserted or updated.

Static cache:

The static cache mentioned here refers to static, directly generating text files such as HTML or XML, and regenerating them when there are updates. It is suitable for pages that do not change much, so I won’t talk about it here.

The above content is a code-level solution. I directly CP other frameworks and am too lazy to change. The content is similar, it is easy to do, and can be used in several ways, but the following content is a server-side caching solution, not a code Level, it requires cooperation from multiple parties

Memory cache:

Memcached is a high-performance, distributed memory object PHP caching mechanism system used to reduce database load and improve access speed in dynamic applications.

php buffer:

There are eaccelerator, apc, phpa, xcache, let’s not talk about these. Search a bunch of them and see for yourself. If you know that there is such a thing, it’s OK

MYSQL cache:

This is also considered non-code level. Classic databases use this method. Look at the running time below, 0.09xxx and the like
I will post a section of my.ini modified by the guy in blue. The 2G MYISAM table can be around 0.05S. It is said that he modified it for almost a year

Reverse proxy based web caching:

Such as Nginx, SQUID, mod_proxy (apache2 and above are divided into mod_proxy and mod_cache)
Example of NGINX

DNS polling:

BIND is an open source DNS server software. This is a big deal to mention. Just search it yourself and everyone knows that it exists.
I know that some large websites such as chinacache do this. To put it simply, it is multi-server. The same page or file is cached on different servers and automatically parsed to the relevant server according to the north and south.