Hello,
Let me first describe my business scenario:
My WordPress website has over 2 million posts, and I’ve done extensive performance optimizations. However, despite these efforts, occasional high-concurrency dynamic requests still cause CPU spikes on the server.
To handle this, I pre-generate static cache for all posts and set a very large TTL value. Most of my posts don’t need to be updated, so I prefer the cache never to expire, only refreshing a few manually when necessary. Also, for the sake of stability, I don’t update to the latest plugin versions.
My questions are:
1.Does the file /usr/local/lsws/cachedata/.cacheman.shm have a maximum size limit? It’s about to exceed 100 MB.
2.For this kind of use case, has there been any consideration to change the cache expiration timestamp data type to unsigned int or bigint?
(Reference: https://wordpress.org/support/topic...eeds-400000000-possible-int32-overflow-issue/)
Thank you.
Let me first describe my business scenario:
My WordPress website has over 2 million posts, and I’ve done extensive performance optimizations. However, despite these efforts, occasional high-concurrency dynamic requests still cause CPU spikes on the server.
To handle this, I pre-generate static cache for all posts and set a very large TTL value. Most of my posts don’t need to be updated, so I prefer the cache never to expire, only refreshing a few manually when necessary. Also, for the sake of stability, I don’t update to the latest plugin versions.
My questions are:
1.Does the file /usr/local/lsws/cachedata/.cacheman.shm have a maximum size limit? It’s about to exceed 100 MB.
2.For this kind of use case, has there been any consideration to change the cache expiration timestamp data type to unsigned int or bigint?
(Reference: https://wordpress.org/support/topic...eeds-400000000-possible-int32-overflow-issue/)
Thank you.
