What hardwre are you using for the client and the server? are you running
ab from localhost? What options are you using with ab?
Most of the CPU cycles in each transaction are going to be spent in the SSL
handshake. I just did a quick test of one of my servers running 1.3.37 on a
dual Xeon 3.0
I found a couple of messages about this in the archives, but I don't see any
responses. It looks like the sigalarm timeout handler is getting called
while SSL is blocked in write(), the SSL context is free()'d in the timeout
handler, and finally when the handler returns to where we were blocked,
o
