I found myself in a situation again.And we know google is in love with pages that load fast.
Since I run a server with apache and Cpanel, I configured it to rotate apache logs every 24 hours (thats the highest setting for cpanel).
Here's where the problem starts:
Apache restarts daily. - Luckily I made a hack in the server to turn that restart to graceful.After the restart, the SSL cache resets despite using 7-day cache lifetime settings.I'm using the socache_shmcb_module module that comes with apache to cache the SSL data.Google may be picking up on this and might be why I may rank lower on https sites.I also run the logs on a ram drive to add speed to the server but the ram drive size is limited (to about 200MB).
Which means my choices are the following:
- Do nothing and let slowdowns occur once per https page per day,
- Pipe to rotatelogs program that's shipped with apache,
- Copy #1 but attempt to load all external pages from within the server immediately,
- Disable log rotation and pray the server doesn't break from lack of free disk space.
If I chose option #2, then how much additional overhead would I face? Because I think executing program functions to write a line is more expensive than simply writing a line to a file.
#3 is tempting as I could force the slowdown to be a minute or so as I re-prime the SSL cache, but I don't know what time of day cpanel tries restarting apache.
What option do you guys think I should use and why?