Performante Web-Apps [de]

... mit Varnish & Co - getITtogether Feb. 2014 Berlin - 15min Talk; gekürzte Online Version.

Transcript

1. Performante Web Apps mit Varnish & Co. Christoph Lühr / @chluehr getITtogether - Berlin 2014
2. Christoph Lühr Head of Development
3. basilicom SEIT 2000
4. Image source: http://www.flickr.com/photos/ethanlindsey/321225525/ CC BY 2.0
5. DEV
7. (#) Internet
9. Unicode Character 'HAPPY PERSON RAISING ONE HAND' (U+1F64B)
10. 1 2 3
11. Performante Web-Apps
12. statisch dynamisch
13. Performance ➊ ➋ ➌
14. ➊
15. Transfer-Rate
16. Transfer-Rate
17. ➋
18. Latenz
19. RENDER C NETWORK D
20. ➌
21. X
22. X
23. x Faktoren
24. CPU RAM HDD NETZ
25. CPU RAM HDD NETZ
26. t
27. t
28. CPU RAM HDD NETZ
29. R A M
30. R A M
31. CPU RAM HDD LAN = IO
32. IO
33. IO
34. RAM SSD WAN HDD LAN 0.05 μs 5 μs x100 x100 50 μs x1.000 x10 5000 μs x100.000 x100 500000 μs x10.000.000 x100
35. IO
36. CACHE
38. IO Queue + Worker
39. t
40. statisch dynamisch
41. statisch dynamisch
43. Reverse- Proxy
44. Varnish
45. Varnish
46. Varnish
47. Varnish
50. Multiple Backends
51. Varnish
52. Varnish
53. Varnish
54. Varnish
55. Varnish
56. Varnish
57. Partielles Caching Edge Side Inc.
58. Varnish
59. Varnish
60. FUBAR? Nachteile
61. • Content++ = RAM++ Hardwareanforderungen • !SSL Workaround: Pound Offloader • Purge / Warm-Up Management • Konfiguration VCL
62. Ratiopharm? Alternativen
64. CDN Content Delivery Network
65. Fallstudie / Beispiel Adventskalender
70. App Größe 2.6 MB
71. HTTP Requests 16 Req/App
74. js js js js js js js js js js js js
75. Ladezeit bei >6 Mbit 1-3 s
77. Transferrate ~300 Mbit/s
78. Peak Transfer (max.) ( ~4000 Mbit/s )
79. Transfervolumen / Top-H ~500 GB
80. HTTP Zugriffe 260 Req/s
81. System: Eine VM. (Varnish, Pound, Apache/PHP)
85. CPU RAM HDD NETZ CPU RAM HDD NETZ CPU RAM HDD NETZ
87. Christoph Lühr email: christoph.luehr@basilicom.de twitter: @chluehr web: http://basilicom.de ! ? basilicom