Status Update
Comments
as...@google.com <as...@google.com> #2
Hi Josh, friendly ping for an update on progress
en...@google.com <en...@google.com> #3
i think the TL;DR is that this is stuck behind investigating the current lab outages, which are more urgent.
pending CL is
do...@google.com <do...@google.com> #4
lo...@google.com <lo...@google.com> #5
jm...@google.com <jm...@google.com> #6
Hmm, gerrit-watcher didn't post the CLs on this bug, so I guess I'll do so manually:
Throughput numbers from a device:
none brotli lz4
USB 3.0 120 110 190
USB 2.0 38 75 63
I'm seeing identical throughput with brotli quality 0 and 1 (110MB/s end to end), although there's some giant low hanging fruit to compress multiple files at once.
zstd isn't in the tree yet (I started the ball rolling on that, but no idea when it'll end up getting merged), but I'll take a look at it eventually, probably when I get around to implementing compression for generic streams in adb (
This is probably good enough to call this fixed for now.
Description
I implemented brotli compression in 3 out of 4 directions (adbd can push/pull, adb can only pull) in
At the default compression level, it's *slow*: a 1GB file of zeroes takes over a minute to compress *on my workstation*. At compression level 1, it's actually a marginal improvement over localhost, so it's probably a reasonable gain over a slow transport, but I just bricked the walleye on my workstation somehow, so I don't have any actual numbers yet.
TODOs:
implement the remaining direction
add a flag to turn it on/off
train a dictionary from adb sync?
look into other algorithms?