We did use stud for a short time but have recently moved back to this approach for a couple of reasons:
+ Currently out SSL connections need to be pinned to a specific server, so we wound up running the terminator on the same box. We then ran into a problem of having more than 65k connections (src ip/port <-> dest ip/port) on loopback, which introduced a bit more complexity in our deployment (either have stud use 127.0.0.2, 127.0.0.3, etc or have stud point to a different port.)
+ The memory consumption also goes up across the board since we are on the same box (2x the connections per actual connection). stud uses an additional ~200k per connection and on some of our boxes that have 100k+ connections, this is something north of 18GB. This was the biggest driver for the change.
+ Currently out SSL connections need to be pinned to a specific server, so we wound up running the terminator on the same box. We then ran into a problem of having more than 65k connections (src ip/port <-> dest ip/port) on loopback, which introduced a bit more complexity in our deployment (either have stud use 127.0.0.2, 127.0.0.3, etc or have stud point to a different port.)
+ The memory consumption also goes up across the board since we are on the same box (2x the connections per actual connection). stud uses an additional ~200k per connection and on some of our boxes that have 100k+ connections, this is something north of 18GB. This was the biggest driver for the change.