In general, what application scenarios does memcached-php use pageCage, memCache, RedisCache, and SSDBCache cache correspond?

The main problem is to think about it. In actual application scenarios, my team will do pageCache cache processing for some pages with fewer page views, however, some pages that are barely visible do not even contain cache, but memCache cache is set for some pages with a large number of views, and for core business pages... the main problem is to think about it. In actual application scenarios, my team will do pageCache cache processing for some pages with fewer page views, however, some pages that are barely viewed do not even have no cache, but memCache cache is set for some pages with a large number of views, for core business pages, pageCache + SSDBCache cache is used for pages with large page views.

The purpose of using the cache is obviously to reduce the server pressure and database read pressure, but the usage of the cache cannot be abused, so I am confused about the usage of these caches: what are their most suitable application scenarios?

Details:
1. What are the best application scenarios of the above four cache technologies?
2. What do you think is the best Cache Policy?
3. What cache mechanisms do you like?

Note: during the development of my team, I encountered obfuscation of cache applications, misuse of cache, or lack of knowledge about which cache policies should be used in the corresponding scenario (no best cache policy is available, only the most suitable one ). Thanks to all the experts, you can leave it alone in PHP. Because programming languages are basically the same, they are all derived from the same class. (* ^__ ^ *) You can answer a certain question, hope Daniel can solve all problems. Thank you. . .

Reply content:

The main problem is to think about it. In actual application scenarios, my team will do pageCache cache processing for some pages with fewer page views, however, some pages that are barely viewed do not even have no cache, but memCache cache is set for some pages with a large number of views, for core business pages, pageCache + SSDBCache cache is used for pages with large page views.

The purpose of using the cache is obviously to reduce the server pressure and database read pressure, but the usage of the cache cannot be abused, so I am confused about the usage of these caches: what are their most suitable application scenarios?

Details:
1. What are the best application scenarios of the above four cache technologies?
2. What do you think is the best Cache Policy?
3. What cache mechanisms do you like?

Note: during the development of my team, I encountered obfuscation of cache applications, misuse of cache, or lack of knowledge about which cache policies should be used in the corresponding scenario (no best cache policy is available, only the most suitable one ). Thanks to all the experts, you can leave it alone in PHP. Because programming languages are basically the same, they are all derived from the same class. (* ^__ ^ *) You can answer a certain question, hope Daniel can solve all problems. Thank you. . .

What is pagecache called filecache?

The question of the subject is simply described as follows: 1. Too many questions. 2 and 3, only suitable, no best. It seems a bit nonsense

To put it simply, the probability of using the file format for cache is relatively low. Unless it is a small application and deployed on a single machine, you can consider it. Otherwise, when the cluster is deployed, file storage reading is a big problem, in terms of efficiency, file has IO overhead. Even SSD physical machines (which are already very fast) do not have fast memory.

Memcache is a mainstream solution that has been around for a long time. If it is a session or something, or a simple KV cache, it is a good choice. It can cope with the vast majority of scenarios. In the past few years, it has been facing a lot of NOSQL pressure, some products, such as memcachedb, can also be used. However, the essence of memcache is caching, and it is strongly recommended that you do not implement storage.

Redis is one of the hot topics of nosql, with a bunch of highlights. Many projects are directly used to replace mc. When only kv caches are used, the performance is very similar to mc. Many people are interested in a few points. One is persistence, and only mc can't do it. The other is a rich data structure. The weakness of mc is that only key-value can be used, while redis is doing queue-based broadcast, and there are also well-developed competing states. So if your business is complex, consider redis. However, it is not recommended to use it as a storage device.

What is SSDB... Never touched. Forgive me for comparing low... There is not much nonsense. In general, based on the specific business needs to consider what cache to use and how to cache, let's first find out the current performance bottleneck.