Analyse BrotliFilter behavior |
||||
Issue description
BrotliFilter.Status UMA's show that about 0.5% of requests finish with "In Progress" status and 0.05% with "Error" status.
The same data sliced by platform:
| Windows | Android |
------------+---------+---------+
In progress | 0.57% | 0.29% |
Error | 0.00% | 0.15% |
------------+---------+---------+
Σ | 0.57% | 0.44% |
The sum for Windows and Android looks similar.
This makes me suspicious that it both results may have the same reason:
actual content has invalid (non-brotli) encoding.
To check this I plan to add additional UMA's: one will report if zlib header is detected, the other one will report brotli error code that will allow to understand at what point "corrupted" input is detected.
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 9 2016
This issue is Pri-1 but has already been moved once. Lowering the priority and moving to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 20 2017
| Windows | Android | OS X |
------------+---------+---------+--------|
In progress | 0.069% | 0.193% | 0.067% |
Error | 0.002% | 0.000% | 0.001% |
------------+---------+---------+--------|
Σ | 0.071% | 0.193% | 0.067% |
Error rate on Android improved a lot. Overall "not-Done" rate is 10x lower nowadays. It seems that content producers / proxies has fixed their pipelines.
,
Feb 20 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by bugdroid1@chromium.org
, May 24 2016