On Thu, 30 May 2002, Patrick Dionisio wrote: > Currently, I have a client script that generates n > number of requests to the apache server. The page it > requests is a static page. With SSL turned on, I'm > only able to get at most 7 to 8 requests per second. > With SSL turned off, I am able to get 50+ requests per > second.
Wow, that's still incredibly slow. What kind of CPU and how much RAM are we talking about here? With SSL turned off you should be able to pump out way more RPS than that on a static page. I suggest you tune that first (you should be looking for a number in the hundreds of RPS at least), and *then* focus on SSL. See: http://httpd.apache.org/docs/misc/perf-tuning.html Upgrading to Apache 2.0.x might help, too. :) > I've tried setting SSLMutex to use sem and > SSLSessionCache to > shm:/usr/local/apache/logs/ssl_gcache_data(512000), shmcb can perform better than shmht under stress (shm == shmht in 1.3, shm == shmcb in 2.0, though you can explicitly specify either choice in both versions)... that's probably worth looking into. See the thread http://marc.theaimsgroup.com/?l=apache-modssl&m=98529562629436&w=2 for an explanation of the differences (though some of the information there is out of date by now, eg shmcb is no longer experimental). > but those changes didn't improve the results. It should actually be a rather drastic improvement over other session cache methods. I definitely think you need to concentrate on the rest of Apache first and then come back to looking at SSL tuning. --Cliff ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
