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

Understanding HTTP/2 prioritization

20e958629852b653fad35c99706fc3ac?s=47 Moto Ishizawa
June 15, 2015
Technology
17
4.8k

Understanding HTTP/2 prioritization

20e958629852b653fad35c99706fc3ac?s=128

Moto Ishizawa

June 15, 2015
Tweet

More Decks by Moto Ishizawa

See All by Moto Ishizawa
20e958629852b653fad35c99706fc3ac?s=48 summerwind
0
64
20e958629852b653fad35c99706fc3ac?s=48 summerwind
1
5.1k
20e958629852b653fad35c99706fc3ac?s=48 summerwind
1
530
20e958629852b653fad35c99706fc3ac?s=48 summerwind
5
1.4k
20e958629852b653fad35c99706fc3ac?s=48 summerwind
2
3.1k
20e958629852b653fad35c99706fc3ac?s=48 summerwind
17
2.8k
20e958629852b653fad35c99706fc3ac?s=48 summerwind
1
1.8k
20e958629852b653fad35c99706fc3ac?s=48 summerwind
3
2.1k
20e958629852b653fad35c99706fc3ac?s=48 summerwind
5
3.1k

Other Decks in Technology

See All in Technology
88dae28e3d082236f37db2f5c2db339d?s=48 keropiyo
0
250
19fc8f6113c5c3d86e6176362ff29479?s=48 kanaugust
PRO
0
120
Ad449f3f4e595ade283a30c4f66010be?s=48 seto_hi
3
1.1k
7b3e0dbc0d712ad5df602d9f9e5e4209?s=48 sei88888
11
2.3k
C38fdebd15fe45a85299d6add2fb2810?s=48 blocknoisegenji
0
120
71c9ebde850996d2533c5df4df2c93c6?s=48 opdavies
0
160
64a4ba69d50590e592cd8e572454daa8?s=48 olegkovalov
1
330
7975b9fd58c8945ae1c6b38747de7f28?s=48 line_developers_tw2
0
490
19fc8f6113c5c3d86e6176362ff29479?s=48 kanaugust
PRO
0
140
3115a782126be714b5f94d24073c957d?s=48 oracle4engineer
0
150
2b680c5f22146e764e2998dd4595ec93?s=48 sue445
0
120
67683b0a8d24009c731787b49881a9de?s=48 tomuro
0
220

Featured

See All Featured
245cee81a9c424266e5e401d844ea881?s=48 lara
17
2.9k
20bfe76b3d6105641f879fe45cfc9272?s=48 bkeepers
PRO
54
4.3k
78b475797a14c84799063c7cd073962f?s=48 holman
448
140k
Ae14cc4491ac334f9cd23f9f93b4305e?s=48 orderedlist
PRO
331
36k
5ce91fa49a613cbc3e20d5f96856473f?s=48 edds
56
9.4k
1f74b13f1e5c6c69cb5d7fbaabb1e2cb?s=48 sferik
613
55k
24fc194843a71f10949be18d5a692682?s=48 gr2m
85
11k
7653c7c449918ff6542880a8c284f5e7?s=48 jponch
103
5.1k
C0390e8b11079f8761c0cd3274ed61cb?s=48 productmarketing
7
820
4394ceb8b277f35ee3da7030384efb5d?s=48 davidbonilla
71
3.6k
B3d6434763caa0ef5dc4b792662c49f7?s=48 smashingmag
233
18k
7fa6101cd43067653cf4ac6c7ca54305?s=48 akmur
252
19k

Transcript

  1. Understanding HTTP/2 prioritization Moto Ishizawa @summerwind

  2. Who? :-) • Platform Engineer @ Yahoo! JAPAN • Beacon

    platforms, Data pipelines • Reviewer of HPBN Japanese Edition • Sections: HTTP/1.1, HTTP/2, WebRTC • HTTP/2 Japan Community • RFC7540 Japanese Translation, h2spec

  3. HTTP/2 Prioritization • HTTP/2 client controls the transmission order of

    resources by priority • Priority is expressed by dependency and weight • Priority is a hint, server may ignore it • In the browser, there is a possibility that the priority affects the rendering • Prioritization might adversely affect the critical rendering path

  4. Priority Tree 0 3 128 5 64 7 16 9

    16 Stream ID Weight Dependency

  5. Priority Tree 0 3 128 5 64 7 16 9

    16 All streams are set weight 16 by default. All streams depend on the Stream ID 0 by default.

  6. Priority Tree 0 3 128 5 64 7 16 9

    16 The priority of the stream is determined by the relative proportions of the weights. Stream ID 3 should receive two-thirds of available resources. The priority of the stream that depends on another stream is determined by the weight of dependent stream. Stream ID 7 should receive half of the resources of Stream ID 3.

  7. Implementation status Server Name Version Support nghttp2 1.0.2 YES H2O

    1.2.0 YES Apache Traffic Server 5.3.0 NO Browser Name Version Support Firefox 38.0.5 YES Chrome 43.0.2357.65 YES (Weight only) Edge 0.11.10074.0 (Preview) NO Safari 9,0 (Preview) NO

  8. Testing the prioritization of browsers • Test page • CSS

    in the <head> × 3 • Javascript in the <head> × 3 • JavaScript in the <body> × 3 • Image in the <body> × 3 • Size of all resources: 100KB • Server • nghttpx v1.0.1 <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Test</title> <link href="tests/1.css" rel="stylesheet"> <link href="tests/2.css" rel="stylesheet"> <link href="tests/3.css" rel="stylesheet"> <script src="tests/1.js"></script> <script src="tests/2.js"></script> <script src="tests/3.js"></script> </head> <body> <h1>Test</h1> <img src=“tests/1.jpg” alt="1"> <img src=“tests/2.jpg“ alt="2"> <img src=“tests/3.jpg” alt="3"> <script src="tests/4.js"></script> <script src="tests/5.js"></script> <script src="tests/6.js"></script> </body> </html>

  9. Firefox’s Priority Tree 9 1. Initialization 0 3 7 201

    1 1 11 1 5 101 Initializing the priority tree by PRIORITY frames.

  10. Firefox’s Priority Tree 9 2. HTML 0 3 7 201

    1 1 13 32 11 1 5 101 Stream for HTML. Prioritized by HEADERS frame.

  11. Firefox’s Priority Tree 9 3. CSS 0 3 7 201

    1 1 13 32 19 32 17 32 15 32 11 1 5 101 Streams for CSS.
 Prioritized by HEADERS frames.

  12. Firefox’s Priority Tree 9 25 4. JavaScript in the <head>

    0 3 7 201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 5 101 Streams for JavaScript.
 Prioritized by HEADERS frames.

  13. Firefox’s Priority Tree 9 25 5. Image 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 5 101 Streams for Image. Prioritized by HEADERS frames.

  14. Firefox’s Priority Tree 9 25 6. JavaScript in the <body>

    0 3 7 201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101 Streams for JavaScript. Prioritized by HEADERS frames.

  15. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  16. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  17. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  18. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  19. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  20. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  21. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  22. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  23. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  24. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  25. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  26. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  27. Firefox’s Priority Tree 9 25 7. Download 0 3 7

    201 1 1 32 13 32 19 32 21 32 23 32 17 32 15 32 11 1 27 22 29 22 31 22 35 32 37 32 33 32 5 101

  28. Firefox’s Timeline 13 15 17 19 21 23 25 27

    29 31 33 35 37 HEADERS (Request) HEADERS (Response) DATA

  29. Chrome’s Priority Tree 1. HTML 0 1 256 Stream for

    HTML. Prioritized by HEADERS frame.

  30. 5 Chrome’s Priority Tree 2. CSS 0 1 256 3

    220 220 7 220 Streams for CSS.
 Prioritized by HEADERS frames.

  31. 5 Chrome’s Priority Tree 3. JavaScript in the <head> 0

    1 256 3 220 220 7 220 9 183 11 183 13 183 Streams for JavaScript. Prioritized by HEADERS frames.

  32. 5 Chrome’s Priority Tree 4. JavaScript in the <body> 0

    1 256 15 183 17 183 19 183 3 220 220 7 220 9 183 11 183 13 183 Streams for JavaScript. Prioritized by HEADERS frames.

  33. 5 Chrome’s Priority Tree 5. Image 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 Streams for Image. Prioritized by HEADERS frames. 15 183 17 183 19 183

  34. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  35. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  36. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  37. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  38. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  39. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  40. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  41. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  42. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  43. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  44. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  45. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  46. 5 Chrome’s Priority Tree 6. Download 0 1 256 3

    220 220 7 220 9 183 11 183 13 183 21 110 23 110 25 110 15 183 17 183 19 183

  47. Chrome’s Timeline 1 3 5 7 9 11 13 15

    17 19 21 23 25 HEADERS (Request) HEADERS (Response) DATA

  48. Edge’s Priority Tree 1. HTML 0 1 16

  49. 5 Edge’s Priority Tree 2. CSS, JavaScript, Image 0 1

    16 15 16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16 Streams for CSS, JavaScript, and Image.
 Priority is not specified. Default value is used.

  50. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  51. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  52. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  53. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  54. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  55. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  56. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  57. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  58. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  59. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  60. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  61. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  62. 5 Edge’s Priority Tree 3. Download 0 1 16 15

    16 17 16 19 16 3 16 16 7 16 9 16 11 16 13 16 21 16 23 16 25 16

  63. Edge’s Timeline 1 3 5 7 9 11 13 15

    17 19 21 23 25 HEADERS (Request) HEADERS (Response) DATA

  64. The prioritization strategy of browsers • Firefox builds the priority

    tree that is optimized for Web pages • Priority order: CSS, JavaScript, Images • Chrome reuses the prioritization strategy of SPDY era that is used only weight • The difference in weight is small… there is room for optimization! • Edge does not support the prioritization • It seems to control the download of the resource by the timing of request...

  65. Conclusion • HTTP/2 prioritization consists of dependency and weight •

    Client notifies the priority, server builds the priority tree • Each browser have different prioritization strategy • The use of priority dependencies may produce better results • Need to measurement the effect of HTTP/2 prioritization! • But there is no tool that can measure the prioritization of HTTP/2...

  66. Thanks!