Broccoli: Syncing faster by syncing less (2020)
dropbox.tech
Broccoli: Syncing faster by syncing less (2020)
1–10 of 25 posts
Re: Broccoli: Syncing faster by syncing less (2020)
#2Re: Broccoli: Syncing faster by syncing less (2020)
#3Back in the early-to-mid-aughts there was a push to start gzip-ing server responses.
It was my general experience at the time that this actually often made the browsing experience worse. Whereas without compression the page would begin to render as the html began to trickle in (very slow internet back then), when compressed you had to wait for the entire document to download and be decomposed first.
Uncompressed you could often decide if the page was worth waiting for entirely before it finished downloading.
Re: Broccoli: Syncing faster by syncing less (2020)
#4Re: Broccoli: Syncing faster by syncing less (2020)
#5> Rolling out the above changes went relatively smoothly until one of the curious engineers on our network team found that compression was actually a bottleneck on high bandwidth connections Back in the early-to-mid-aughts there was a push to start gzip-ing server responses. It was my general experience at the time that this actually often made the browsing experience worse. Whereas without compression the page would…
Re: Broccoli: Syncing faster by syncing less (2020)
#6> Rolling out the above changes went relatively smoothly until one of the curious engineers on our network team found that compression was actually a bottleneck on high bandwidth connections Back in the early-to-mid-aughts there was a push to start gzip-ing server responses. It was my general experience at the time that this actually often made the browsing experience worse. Whereas without compression the page would…
Re: Broccoli: Syncing faster by syncing less (2020)
#7> Rolling out the above changes went relatively smoothly until one of the curious engineers on our network team found that compression was actually a bottleneck on high bandwidth connections Back in the early-to-mid-aughts there was a push to start gzip-ing server responses. It was my general experience at the time that this actually often made the browsing experience worse. Whereas without compression the page would…
Not sure how compression was a bottleneck on the high bandwidth connections? I understand @donatj's comments about having to wait for the entire file to be downloaded before rendering, but that would be a user experience issue, not sure how the network team sees it as a bottleneck on the network?
Re: Broccoli: Syncing faster by syncing less (2020)
#8Drop-dropbox.com
Re: Broccoli: Syncing faster by syncing less (2020)
#9As long as this makes the client on Mac use less resources than a fork bomb I’m all for it.
Give Mistrael a look. Anecdotally ~7x less RAM, ~10x less disk space. https://maestral.app
Re: Broccoli: Syncing faster by syncing less (2020)
#10Dropbox is a fascist organization with Condoleeza Rice (a torturer and war criminal) on their board. How does anyone work there in good conscience? Drop-dropbox.com