News for hackers. Stuff that matters.

A comment on Porting my website to Workers Sites and Zola. Parent comment

Re:Porting my website to Workers Sites and Zola by EatonZ on Friday September 27, 2019 @09:52PM (#21097857)
As a workaround maybe you could, behind the scenes, split large files into 2 (or more) key-value pairs, and then bill appropriately for the use of 2 key-value pairs instead of just 1.
[ Parent | on HN ]
Re:Porting my website to Workers Sites and Zola by steveklabnik on Saturday September 28, 2019 @10:33AM (#21100474)
Possibly, yeah! You won't necessarily get a ton of speed that way...
[ Parent | on HN ]
Re:Porting my website to Workers Sites and Zola by judge2020 on Saturday September 28, 2019 @11:13AM (#21100733)
This is how my file stitching logic works, and it's actually pretty fast (some reported 2mbps-30mbps depending if the DC had those keys locally cached), it's just incrementally more expensive for each 2mb increase in file size. https://github.com/judge2020/cloudflare-file-hosting/tree/dd... But it might be a little much for this to be a first-party solution.
[ Parent | on HN ]
Re:Porting my website to Workers Sites and Zola by steveklabnik on Saturday September 28, 2019 @02:17PM (#21101943)
Thanks for the tip. By the way, line 84 introduces some unneeded serialization; you could get some more speed there by fetching the bits in parallel.
[ Parent | on HN ]