3 ms·
This was possibly true 10-20 years ago (SSL is that old). It is no longer reasonable and is usually just an excuse. That said, in my experience, native SSL/TLS
by bkeroack 12y ago
This was possibly true 10-20 years ago (SSL is that old). It is no longer reasonable and is usually just an excuse.
That said, in my experience, native SSL/TLS within IIS is incredibly slow/inefficient. Running on 2012R2 (so a modern version), terminating SSL at IIS resulted in me being able to trivially peg the server's CPU using Apache Ab on my laptop. So clearly you need a good implementation.