Skip to content

Comment on Optimizing Linux Memory Management for Low-latency, High-throughput Databasesparent

Comments

I understood it to mean that it had 1/4 the error rates they were previously seeing.

Huh, that's not even one I considered. I guessed 1/5, so the change was 4x the final value. Either way it's wrong - "dropped by X%" should be calculated as (original - final) / original.

This is exactly right :)

Then it dropped by 75%.

Yes. It was a blunder. The post has been updated to reflect this.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.