Better performances on the server side with HTTP/2

Better performances with HTTP/2 and Eclipse Vert.x Thomas Segismont, Senior
Software Engineer, Red Hat

Agenda • Improving web performance with HTTP/2 • Scalable service
architectures with HTTP/2

Who am I? • tsegismont @ GitHub / Twitter /
Gmail / Freenode • Vert.x core team since August 2016 • At Red Hat since November 2012 (RHQ and Hawkular)

IMPROVING WEB PERFORMANCE WITH HTTP/2

Latency matters more! 1000 1550 2100 2650 3200 3750 1000
1750 2500 3250 4000

HTTP1/TCP impedance mismatch • 3-way handshake • Congestion control •
Slow start • Congestion window => Optimized for long-lived connections Websites: a lot of small-medium sized resources

HTTP/1 Optimization techniques • Persistent connections • Multiple connections •
Domain sharding • CDN • Browser caching • Compression / minification and concatenation

Still a bottleneck! GET OK GET OK

HTTP/2 • A better TCP transport for actual HTTP request
and responses • Same HTTP semantics • RFC7540 : Hypertext Protocol version 2 • RFC7541 : Header Compression for HTTP/2

HTTP/2 • H2 – TLS/SSL – Mandatory for browsers –
ALPN extension to negotiate HTTP/1 or HTTP/2 • H2C – Clear – Via HTTP/1 upgrade or directly

Framed protocol • Defines a set of frames encoded in
binary on a single connection – Settings – Headers – Data – Flow control – Push, Priority, Ping – Reset

Settings frames • First frame exchanged by client and server
– Max concurrency – Max frame size – … etc

GET /index.html HTTP/1.1\r\n Host: www.free.fr\r\n User-Agent: Mozilla/5.0\r\n Accept-Encoding: text/html\r\n Accept-Language:
en-US\r\n \r\n 00003501250000000300 0000000f824488355217 caf3a69a3f874189f1e3 c2f2d852af2d9f7a88d0 7f66a281b0dae0508749 7ca589d34d1f51842d4b 70dd Request headers 2x smaller length type flags stream_id

Subsequent request headers 4x smaller GET /products.html HTTP/1.1\r\n Host: www.free.fr\r\n
User-Agent: Mozilla/5.0\r\n Accept-Encoding: text/html\r\n Accept-Language: en-US\r\n \r\n 00001701250000000500 0000000f82448aaec3c9 691285e74d347f87c2c1 c0bf

Response headers + data HTTP/1.1 200 OK\r\n Content-Type: text/html\r\n Cache-Control:
max-age=86400\r\n Content-Length: 37\r\n \r\n <html><body>Hello World </body></html> 00001f01240000000300 0000000f885f87497ca5 89d34d1f588aa47e561c c581e71a003f5c023337 0000250001000000033c 68746d6c3e3c626f6479 3e48656c6c6f20576f72 6c643c2f626f64793e3c 2f68746d6c3e length type flags stream_id

SCALABLE SERVICES WITH HTTP/2

Target architectures service service service service gateway gateway backend backend
service service backend backend

Constraints • 1ms ping • 1G < bandwidth < 10G
• 1ms < service time < 200ms • 200b < body size < 2kb

HTTP/1.1 vs HTTP/2 server server HTTP/1 vs HTTP/2 backend backend
client client 20 ms think time

0 100 200 300 400 500 600 700 800 0
200 400 600 800 HTTP/1 - 8 connections planned (req / sec) performed (req/sec)

HTTP/1.1 Head Of Line Blocking Client Server }20ms Backend }

0 100 200 300 400 500 600 700 800 900
1000 1100 1200 0 300 600 900 1200 HTTP/1 - 8 connections HTTP/2 - 1 connection / max_concurrent_streams 20 planned (req / sec) performed (req / sec)

HTTP/2.0 Multiplexing Client Server } 20ms Backend } }

Thread pool concurrency

0 1000 2000 3000 4000 5000 0 1250 2500 3750
5000 HTTP/2 thread pool planned (req / sec) performed (req / sec)

Eclipse Vert.x is a toolkit for building reactive and polyglot
applications for the JVM

Toolkit • Embeddable • Composable • Modular • Minimum dependencies
• Classloading / Injection free

Polyglot

Reactive • Non blocking • Event driven • Distributed •
Rxified APIs • Reactive-streams

HTTP/2 with Vert.x • Client / Server • h2 /
h2c • HTTP Request / response API • HTTP/2 specific features for extensions

Event Driven • NIO selectors • Disk operations • Timers
• Messages • Database • … etc

Reactor pattern with Event Loop Single thread

Event loop benefits • Easier to scale • Mechanical sympathetic
• Simple concurrency model

Event loop concurrency

0 1000 2000 3000 4000 5000 0 1250 2500 3750
5000 HTTP/2 thread pool HTTP/2 non blocking planned (req / sec) performed (req / sec)

Multi-reactor pattern

Conclusion • Unleash concurrency with HTTP/2 • Keep the good
old HTTP/1 semantics • Non blocking is a key factor for high concurrency • Vert.x is a great fit for HTTP/2 – Reactive ecosystem – Easy to scale

Thank you

Links • http://vertx.io • https://github.com/vietj/http2-bench • http://www.belshe.com/2010/05/24/more-bandwidth-doesnt- matter-much/ • https://www.infoq.com/presentations/latency-pitfalls
• https://hpbn.co

Better performances on the server side with HTTP/2

Better performances on the server side with HTTP/2

More Decks by Thomas Segismont

Other Decks in Technology

Featured

Transcript