5 ms·
Seems to remarkably decrease latency (380ms -> 109ms). Running some tests: # ab -n 400 http://nlb-34dc3b430638dc3e.elb.us-west-2.amazonaws.com/ Time pe
by syncerr 9y ago
Seems to remarkably decrease latency (380ms -> 109ms). Running some tests:
# ab -n 400 http://nlb-34dc3b430638dc3e.elb.us-west-2.amazonaws.com/
Time per request: 108.779 [ms] (mean, across all concurrent requests)
# ab -n 400 <public server via ELB>
381.933
# ab -n 400 <public server via ALB>
380.632
# (for reference) ab -n 400 https://www.google.com/
190.536
# (for reference) ab -n 400 https://sandbox-api.uber.com/health/
107.680
If you're wiling to terminate SSL, this looks like it could be a solid improvement.
- geocar 9y agoI've seen a similar improvement using the EnableProxyProtocol policy, which required a bit of code: Time per request: 88.400 [ms] (mean, across all concurrent requests) versus public server via the regular HTTP proxy: Time per request: 415.859 [ms] (mean, across all concurrent requests) For reference: $ ab -n 400 https://www.google.com/ Time per request: 168.438 [ms] (mean, across all concurrent requests)