3 ms·
A large website wants to have its current content cached as much as possible—ideally very few users should be hitting the CMS directly—but it doesn't make sense
by lolinder 3y ago
A large website wants to have its current content cached as much as possible—ideally very few users should be hitting the CMS directly—but it doesn't make sense to cache content from 1995 on the off chance that today is the day someone needs it. In fact, to speed up database performance on your current content it may even make sense to store your archives in a different, less beefy database.
However, if Google penalizes slow performance on any page, even archives, these strategies could damage your search rankings even for your current content.