On Friday, June 01, 2012 01:56:23 PM John D. Mitchell wrote: > Is this over and above the usual large tax from using SSL? > > Does the CPU stay pegged for a long time after a single request (i.e. what > do you mean by "awhile")? > > Are you running this on bare metal or in a virtual instance somewhere? > Running SSL on e.g. low-end ec2 instances is a Bad Idea(tm).
It's on an ec2 small, but I don't think that's the issue. There is no traffic, and mongrel2 just spins out of control. I've discovered that if I start mongrel2 and connect to the https port and close the connection without performing an ssl handshake, then mongrel2 goes to 100% cpu. It stays this way about 2 minutes even though there are no connections and no further requests. I can reproduce this every time. It is the act of closing that trips it out. If I sit there with the connection open and do nothing, then all is well. I do not get this problem if I connect+close on a non-ssl mongrel2. Performing full https requests seem to be fine. Requesting a resource that results in a long poll and then closing the connection is also fine. Justin
