Tweet
After implementing a new look and feel for one of my sites (a big community, 20K+ members, 1M+ posts), the thing began running like a dog. Server loads were very low (less than 1.0, even with 200-400 members on at any time). Couldn't figure it out. Sooooo ....
1) I optimized my new graphics. Ah, there was some space savings there. But, no dice. Site still ran slower than hell.
2) I tweaked my Apache configuration until I was blue in the face. Couldn't get any love.
Turns out, my images were not being cached because I enabled Apache's "cookie logging" capabilities (mod_usertrack). When you do this, each and every request from your web server will be accompanied by a cookie request. In most browsers, this will automatically render the object (image, page, etc) as un-cacheable.
Disabled my cookie logging, voila. I'm off to the races again. Life is good.
Hope this helps some folks out there - it drove me crazy. I saw several of you posting similar questions, so I thought I'd share.
Cheers.
1) I optimized my new graphics. Ah, there was some space savings there. But, no dice. Site still ran slower than hell.
2) I tweaked my Apache configuration until I was blue in the face. Couldn't get any love.
Turns out, my images were not being cached because I enabled Apache's "cookie logging" capabilities (mod_usertrack). When you do this, each and every request from your web server will be accompanied by a cookie request. In most browsers, this will automatically render the object (image, page, etc) as un-cacheable.
Disabled my cookie logging, voila. I'm off to the races again. Life is good.
Hope this helps some folks out there - it drove me crazy. I saw several of you posting similar questions, so I thought I'd share.
Cheers.
Comment