Broccoli: Syncing Faster by Syncing Less
dropbox.tech
Broccoli: Syncing Faster by Syncing Less
1–10 of 58 posts
Re: Broccoli: Syncing Faster by Syncing Less
#2Hi folks, I'm Daniel from Dropbox, and I am happy to answer any questions about this tech.
Re: Broccoli: Syncing Faster by Syncing Less
#3None of the images are loading. :(
Re: Broccoli: Syncing Faster by Syncing Less
#4None of the images are loading. :(
Should be fixed now :)
Re: Broccoli: Syncing Faster by Syncing Less
#5The header on the page keeps hiding and reappearing as I scroll making it incredibly difficult to read.
Re: Broccoli: Syncing Faster by Syncing Less
#6I'm more of a security-focused engineer so I'm most interested in the "specially crafted low-privilege jail". What protocol gets data in and out, not shared memory I'm sure? Do the jail processes also have to implement an RPC server (protobuf/gRPC/HTTP?) or is there another mechanism for giving them work and receiving results?
Re: Broccoli: Syncing Faster by Syncing Less
#7Good supporting data
Re: Broccoli: Syncing Faster by Syncing Less
#8I'm more of a security-focused engineer so I'm most interested in the "specially crafted low-privilege jail". What protocol gets data in and out, not shared memory I'm sure? Do the jail processes also have to implement an RPC server (protobuf/gRPC/HTTP?) or is there another mechanism for giving them work and receiving results?
Dropbox uses a similar toolbox as https://chromium.googlesource.com/chromiumos/docs/+/master/s...
And yes, much of the overhead stems from the RPC server that needs to be implemented. For lepton we used a raw TCP server (a simple fork/exec server) to answer compression requests. For Lepton we would establish a connection and send a raw file on the socket and await the compressed file on the same socket. A strict SECCOMP filter was used for lepton. It was nice to avoid this for broccoli since it was implemented in the safe subset of rust.
Re: Broccoli: Syncing Faster by Syncing Less
#9I'm more of a security-focused engineer so I'm most interested in the "specially crafted low-privilege jail". What protocol gets data in and out, not shared memory I'm sure? Do the jail processes also have to implement an RPC server (protobuf/gRPC/HTTP?) or is there another mechanism for giving them work and receiving results?
Dropbox uses a similar toolbox as https://chromium.googlesource.com/chromiumos/docs/+/master/s... And yes, much of the overhead stems from the RPC server that needs to be implemented. For lepton we used a raw TCP server (a simple fork/exec server) to answer compression requests. For Lepton we would establish a connection and send a raw file on the socket and await the compressed file on the same socket. A strict SECC…
Thank you for the technical answer!
Re: Broccoli: Syncing Faster by Syncing Less
#10[deleted]