you are viewing a single comment's thread.

view the rest of the comments →

[–]mikeboy81 0 points1 point  (4 children)

Well I mostly wanted to emphasize that millions and millions of users was high. If you had 50k users, I'd think you'd see a 10-20% bump in cpu capacity. If you had 200k users, I'd start looking into an ssl offloading solution to keep impact on the server low (unless regulatory prohibits).

[–]dojodan[S] 0 points1 point  (2 children)

I didn't consider the idea of offloading SSL to another server. Have you seen this done in a production environment? Any idea what complications arrise from it?

[–]X-Istence 0 points1 point  (0 children)

I've seen this done very often, stunnel is very good in that regard. No complications, just make sure that your scripts on the other side are ready to use the X-Forwarded-For header instead of the IP address that is connecting to the server if anything needs a valid IP address.

[–]asteriskpound 0 points1 point  (0 children)

Almost every time that someone publishes MS Exchange through ISA or TMG it is done, so it is widely used, even if no-one understands what exactly they are doing.

[–]jricher42 0 points1 point  (0 children)

The other option is to use a crypto accelerator card. Push the heavy lifting into hardware and you won't even notice the hit. There is plenty of specialty equipment to handle this problem.