For WSO, we've always gone to two weeks since we have over 300,000 discussions. At any one time, only a few thousand forum URLs are active, so it makes sense to heavily cache the other pages. The downside to this is that when you make any site-wide, template, or design changes, you have to wait two weeks for the changes to be implemented across all URLs.
To keep the cache "warm", we have a specific process that visits all URLs in our sitemap. When a user or Googlebot visits these pages, this increases the likelihood that the page will appear in the cache i.e. our hit rate improves. It also keeps Varnish full of more objects that can be accessed quickly.
As you can see from the graph below, the ratio of “cache hits” green to total hits blue + green is over 93%.
Step 4: Tune your database and focus on your slowest armenia mobile database queries
At WSO, we use a MySQL database. Make sure you enable slow query reporting and check it at least quarterly. Use EXPLAIN to check your slowest queries. Add indexes as needed, and rewrite queries that can be optimized.
At WSO, we use MySQL database. To tune MySQL, you can use the following scripts s:githubommajorMySQLTuner-perl:s:githubommattiabasonetuning-primer
Step 5: Headers
Use 2 server push to send resources to the page before requesting them. Just make sure you test which ones should be pushed first. JavaScript is a good choice for us.