Write-Ahead Logs on S3: Compatibility Is Not Performance (blog.trylle.com) 1 points by Xlab 20d ago ↗ HN
[–] Xlab 20d ago ↗ 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.
[–] catchnear4321 20d ago ↗ > Its asterisk is structural: it is explicitly zonal — a single Availability Zone.hi claude [–] Xlab 20d ago ↗ 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 ;) [–] catchnear4321 20d ago ↗ i-know-the-feeling.meme
[–] Xlab 20d ago ↗ 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 ;) [–] catchnear4321 20d ago ↗ i-know-the-feeling.meme
7 comments
[ 1.1 ms ] story [ 5.5 ms ] threadWe ran an identical CAS write-ahead-log workload against AWS S3, S3 Express One Zone, Tigris, and Cloudflare R2.
Benchmark results available.
hi claude
Supposed to be a hand-made blog post but I had no hands left yesterday ;)