Write-Ahead Logs on S3: Compatibility Is Not Performance

Posted by Xlab on Monday August 24, 2026 @03:27AM
from the blog.trylle.com dept.

https://blog.trylle.com/wal-s3

( 5 comments | 5 points | on HN )

Re:Write-Ahead Logs on S3: Compatibility Is Not Performance by Xlab on Monday August 24, 2026 @03:27AM (#49416288)

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.

[ Parent | on HN ]

Re:Write-Ahead Logs on S3: Compatibility Is Not Performance by fgsbhsbsbdzs on Monday August 24, 2026 @04:20AM (#49416702)

Amazing

[ Parent | on HN ]

Re:Write-Ahead Logs on S3: Compatibility Is Not Performance by catchnear4321 on Monday August 24, 2026 @07:00AM (#49418003)

> Its asterisk is structural: it is explicitly zonal — a single Availability Zone.

hi claude

[ Parent | on HN ]

Re:Write-Ahead Logs on S3: Compatibility Is Not Performance by Xlab on Monday August 24, 2026 @10:16AM (#49420130)

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 ;)

[ Parent | on HN ]

Re:Write-Ahead Logs on S3: Compatibility Is Not Performance by catchnear4321 on Monday August 24, 2026 @11:57AM (#49421628)

i-know-the-feeling.meme

[ Parent | on HN ]