WILS: SSL TPS versus HTTP TPS over SSL

The difference between these two performance metrics is significant so be sure you know which one you’re measuring, and which one you wanted to be measuring.  It may be the case that you...
Published Feb 03, 2010
Version 1.0
acceleration
application delivery
deployment
http
metrics
performance
security
ssl
testing
us
Lori_MacVittie1's avatar
Lori_MacVittie1
Icon for Nimbostratus rankNimbostratus
Apr 07, 2010
James - To count it as new conns per second you'd want to eliminate the data transfer.

 

 

Wildcard - TPS refers to an entire transaction, from handshake to data transfer, to closure. It would be 51 TPS, as you correctly surmise (assuming underlying protocol is HTTP 1.1) although what you end up testing is two things: bulk encryption/decryption rates (for objects received over a persistent connection) with a variable number of handshakes (depending on how many objects are allowed to be retrieved over a single connection).

 

 

SSL is very difficult to quantify because there are two different functions being used: handshaking exchanges keys and performs different RSA operations than the bulk encryption/decryption performed within that SSL session.