Difference in Response time - With Http and Https
Will there be difference in response time of the results ,with an application ,if it has been load tested with HTTP protocal and without HTTP protoal? [img]/images/graemlins/ooo.gif[/img]
Re: Difference in Response time - With Http and Https
In most infrstructure there will be numerous architecture components between the injector and the webserver.
1. HTTPS is not compressible or cachable so the full packet payload has to traverse all components every time it is requested (but see below). On the other hand HTTP is plain text; it can be cached unless the headers or security policies prevent that, and moreover it can be compressed, e.g. zip or gzip or other between compatible compents - net result is that respinse times and bandwidth utilisation will both be less than the corresponding HTTPS version of a page (and associated objects)
2. Encryption/decryption imposes an additional overhead at each end, so the full response time will be higher even if all other factors (see 1.) were identical.
Mitigations for the above can include decrypt/encrypt on the proxy or webcache to allow caching, and compression prior to encryption, and the use of hardware acceleration products, e.g. SSL cards on ISA servers.