Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Performante Web-Apps [de]

Christoph Lühr
February 26, 2014
Programming
1
160

Performante Web-Apps [de]

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

Christoph Lühr

February 26, 2014
Tweet

More Decks by Christoph Lühr

See All by Christoph Lühr
Vektor-Suche & LLMs
chluehr
0
41
Search, Embeddings & Vector-DBs
chluehr
0
64
Reality Check: Automated Content Production at Enterprise Scale with Pimcore
chluehr
0
26
The how and why of getting Freelancers
chluehr
0
58
Content & Master Data Management with Pimcore
chluehr
1
480
Master Data Management with Pimcore
chluehr
0
170
Swoole in 5 Minutes [en]
chluehr
1
12k
PIM & Master Data Management with Pimcore 5 [en]
chluehr
2
280
Digital Transformation & Master Data Management with Pimcore 5
chluehr
0
220

Other Decks in Programming

See All in Programming
CSC305 Lecture 25
javiergs
PRO
0
130
短期間での新規プロダクト開発における「コスパの良い」Goのテスト戦略」 / kamakura.go
n3xem
2
170
モバイルアプリにおける自動テストの導入戦略
ostk0069
0
110
ブラウザ単体でmp4書き出すまで - muddy-web - 2024-12
yue4u
2
460
採用事例の少ないSvelteを選んだ理由と それを正解にするためにやっていること
oekazuma
2
1k
tidymodelsによるtidyな生存時間解析 / Japan.R2024
dropout009
1
770
見えないメモリを観測する: PHP 8.4 `pg_result_memory_size()` とSQL結果のメモリ管理
kentaroutakeda
0
320
生成AIでGitHubソースコード取得して仕様書を作成
shukob
0
330
今年のアップデートで振り返るCDKセキュリティのシフトレフト/2024-cdk-security-shift-left
tomoki10
0
200
103 Early Hints
sugi_0000
1
230
コンテナをたくさん詰め込んだシステムとランタイムの変化
makihiro
1
120
fs2-io を試してたらバグを見つけて直した話
chencmd
0
230

Featured

See All Featured
A better future with KSS
kneath
238
17k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
38
1.9k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
10
810
Learning to Love Humans: Emotional Interface Design
aarron
273
40k
jQuery: Nuts, Bolts and Bling
dougneiner
61
7.5k
A Philosophy of Restraint
colly
203
16k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
665
120k
Building Flexible Design Systems
yeseniaperezcruz
327
38k
Automating Front-end Workflow
addyosmani
1366
200k
Code Review Best Practice
trishagee
65
17k
Building an army of robots
kneath
302
44k
Bash Introduction
62gerente
608
210k

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

  6. None

  7. (#) Internet

  8. None

  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

  37. None

  38. IO Queue + Worker

  39. t

  40. statisch dynamisch

  41. statisch dynamisch

  42. None

  43. Reverse- Proxy

  44. Varnish

  45. Varnish

  46. Varnish

  47. Varnish

  48. None
  49. None

  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

  63. None

  64. CDN Content Delivery Network

  65. Fallstudie / Beispiel Adventskalender

  66. None
  67. None
  68. None
  69. None

  70. App Größe 2.6 MB

  71. HTTP Requests 16 Req/App

  72. None
  73. None

  74. js js js js js js js js js js

    js js

  75. Ladezeit bei >6 Mbit 1-3 s

  76. None

  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)

  82. None
  83. None
  84. None

  85. CPU RAM HDD NETZ CPU RAM HDD NETZ CPU RAM

    HDD NETZ
  86. None

  87. Christoph Lühr email: [email protected] twitter: @chluehr web: http://basilicom.de ! ?

    basilicom