Jepsen: NATS 2.12.1

Why? Why do some databases do that? To have better performance in benchmarks? It’s not like that it’s ok to do that if you have a better default or at least write a lot about it. But especially when you run stuff in a small cluster you get bitten by stuff like that.

Re: Jepsen: NATS 2.12.1

#6

Post by clemlesne » Mon, Dec 08, 2025, 7:41 PM UTC

NATS is a fantastic piece of software. But doc’s unpractical and half backed. That’s a shame to be required to retro engineer the software from GitHub to know the auth schemes.

Re: Jepsen: NATS 2.12.1

#7

Post by thinkharderdev » Mon, Dec 08, 2025, 7:43 PM UTC

merb wrote: post #5

> 3.4 Lazy fsync by Default Why? Why do some databases do that? To have better performance in benchmarks? It’s not like that it’s ok to do that if you have a better default or at least write a lot about it. But especially when you run stuff in a small cluster you get bitten by stuff like that.

> To have better performance in benchmarks

Yes, exactly.

Re: Jepsen: NATS 2.12.1

#8

Post by Infiltrator » Mon, Dec 08, 2025, 7:57 PM UTC

selectodude wrote: post #2

Definitely thought this was about aviation for a moment.

Likewise. It took me a moment to realise Jepsen!== Jeppesen

Re: Jepsen: NATS 2.12.1

#9

Post by gostsamo » Mon, Dec 08, 2025, 7:57 PM UTC

Thanks, those reports are always a quiet pleasure to read even if one is a bit far from the domain.

Re: Jepsen: NATS 2.12.1

#10

Post by belter » Mon, Dec 08, 2025, 8:02 PM UTC

clemlesne wrote: post #6

NATS is a fantastic piece of software. But doc’s unpractical and half backed. That’s a shame to be required to retro engineer the software from GitHub to know the auth schemes.

[flagged]