wsuen

3 ms·

1. 1.▲
   by wsuen 6y ago

   Hi there. Fortunately for the ML team, the Previews team kept a detailed cost breakdown for different preview types - including on the fly generation cost, async generation cost, and cost to serve a preview. Our ballpark accounted for some
2. 2.▲
   by wsuen 6y ago

   Hi joosters, thanks for the question. It is always a good practice to ask if we are solving the right problem. The decision to prewarm is ultimately a product decision to give users a better experience across the many surfaces where they en
3. 3.▲
   by wsuen 6y ago

   I've gotta run, I'll take a look later if other questions come in!
4. 4.▲
   by wsuen 6y ago

   Hi mehrdada. In the article, we discuss how to evaluate tradeoffs of ML projects. One of these tradeoffs is cost of development and deployment vs. cost of not developing a solution. In our particular case, the tradeoff made sense.
5. 5.▲
   by wsuen 6y ago

   Hi setib, great question. The original idea to use heuristics for preview cost reduction came out of a Hack Week project. This led to an initial brainstorm meeting between the ML team and the Previews team about what this might look like as
6. 6.▲
   by wsuen 6y ago

   Hi folks, author here. I am very excited to share this post about how we use machine learning at Dropbox to optimize our document preview generation process. Enjoy! I'll be online for the next hour or so; happy to answer any questions
7. 7.▲
   Machine learning saves us $1.7M a year on document previews(dropbox.tech)

   201 points by wsuen 6y ago|52 comments