"Local Uploads makes upload requests (i.e. PutObject, UploadPart) faster. In both our private beta tests with customers and our synthetic benchmarks, we saw up to 75% reduction in Time to Last Byte (TTLB) when upload requests are made in a different region than the bucket. In these results, TTLB is measured from when R2 receives the upload request to when R2 returns a 200 response."
"With Local Uploads, object data is written close to the client and then copied to the bucket's region by a Cloudflare job running in the background, a so-called replication task. According to the documentation, the file remains immediately available and consistent throughout this process."
"Importantly, the object is immediately accessible after the initial write completes. It remains accessible throughout the entire replication process - there's no waiting period for background replication to finish before the object can be read."
Local Uploads for R2 optimizes write performance by writing object data in the client's region and asynchronously copying it to the bucket's region via background replication tasks. Object metadata is published to the bucket's region immediately while physical storage can reside locally. Upload operations such as PutObject and UploadPart return a 200 response once the initial write completes, and objects remain immediately accessible and consistent during background replication. Private beta and synthetic benchmarks showed up to 75% reduction in Time to Last Byte for cross-region uploads. The system decouples physical storage from logical metadata using a global metadata service on Durable Objects and manages replication with queued tasks and automatic retries.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]