Enable QPACK dynamic table on Android
Categories
(Core :: Networking: HTTP, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox117 | --- | fixed |
People
(Reporter: gregp, Assigned: kershaw)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
QPACK dynamic table was disabled on desktop and mobile in bug 1628460. It was later re-enabled in bug 1655782, but only on desktop.
|
||
Updated•1 year ago
|
|
|
||
Updated•1 year ago
|
|
|
||
Comment 1•1 year ago
|
||
Hey Martin,
Just wanted to check if you had any concerns around re-enabling this on Android.
Thanks.
|
||
Comment 2•1 year ago
|
||
:kershaw can you take a look at this? I think that - given the time involved - the unspecified problem is OK, so we should just turn this back on (and give our Android users better performance).
|
|
||
Comment 3•1 year ago
|
||
Worth noting also: the original table size was 4k for Android. We can probably afford a larger table. 16k at least, though 64k to match desktop is probably fine. Most Android devices have multiple Gb of RAM, so a few kilobytes per connection won't hurt that much. Other decompressors can use a lot more memory than that (zlib uses 40k and that's an old, lightweight algorithm).
|
Assignee | |
Comment 4•1 year ago
|
||
(In reply to Martin Thomson [:mt:] from comment #3)
Worth noting also: the original table size was 4k for Android. We can probably afford a larger table. 16k at least, though 64k to match desktop is probably fine. Most Android devices have multiple Gb of RAM, so a few kilobytes per connection won't hurt that much. Other decompressors can use a lot more memory than that (zlib uses 40k and that's an old, lightweight algorithm).
Thanks. I 64k should be fine. Will submit a patch soon.
|
|
Assignee | |
Comment 5•1 year ago
|
||
|
||
Updated•1 year ago
|
|
||
Comment 7•1 year ago
|
||
| bugherder | ||
Description
•