Write-Ahead Logs on S3: Compatibility Is Not Performanceblog.trylle.com 60 pointsXlab19 days ago5 commentsSaveHideCopy link On HNComments−catchnear432119dIts asterisk is structural: it is explicitly zonal — a single Availability Zone.hi claude−XlabOP19dFun fact: after spending 20+ hours during weekend on waltier, running all suites, I was so burned out that I just yolod almost full article via fable.Supposed to be a hand-made blog post but I had no hands left yesterday ;)−catchnear432119di-know-the-feeling.meme−XlabOP19dFollowing a hot topic of putting WAL on S3, initiated by Cursor blog post.We ran an identical CAS write-ahead-log workload against AWS S3, S3 Express One Zone, Tigris, and Cloudflare R2.Benchmark results available.−fgsbhsbsbdzs19dAmazing
Comments
hi claude
Fun fact: after spending 20+ hours during weekend on waltier, running all suites, I was so burned out that I just yolod almost full article via fable.
Supposed to be a hand-made blog post but I had no hands left yesterday ;)
i-know-the-feeling.meme
Following a hot topic of putting WAL on S3, initiated by Cursor blog post.
We ran an identical CAS write-ahead-log workload against AWS S3, S3 Express One Zone, Tigris, and Cloudflare R2.
Benchmark results available.
Amazing