I Can't Be the Only One
Tomorrow I face the not-so-pleasant task of translating all the nice, shiny front-end configuration work I've done in the past year on our Cherokee server at work into the more standard, "banal" Apache style, as performance with Cherokee in HTTPS (SSL) requests has been depressingly poor.
I'm frustrated with this, though, simply because I can't find any references at all to Cherokee's support (or lack thereof) of "SSL session caching," a feature which, when enabled in Apache, suddenly made a test copy of an app we use daily fly like a bat out of hell (and that's on an Amazon EC2 "micro" instance!). Apache was just as slow as Cherokee in handling SSL-based requests right up until I flipped that session caching switch. Suddenly the "performance hit" was gone -- the first request still took a second or two, but after that things were nice and snappy.
Does anyone out there have any ideas on whether Cherokee even supports this kind of session caching? If it can, how does one actually convince it to do so? I'd rather not spend the bulk of my morning writing
Update: I never did find a fix for this, so I switched everything to Apache. It's all bloody fast now. At least now I can rest easy knowing the internal apps I worked on for the company over the past two years actually are as fast as I thought they should be :)
I'm 
blog comments powered by Disqus