Hacker News Reader

People write bugs occasionally.

You're talking about the person who spent months tracking down what everyone else thought was a code or compiler bug but actually proved was a subtle CPU bug requiring vendor errata releases, and further, who wrote this log-structured, snapshottable, syncable low-memory using, real-world filesystem from scratch for the highly parallel operating system he has been rearchitecting for over 10 years now. There are consistent status update posts outlining the on disk filesystem structure, as well as its relation to the virtual memory subsystem and the in-kernel parallelism feeding IO writes, as well as constant code commits implementing these things, so I'd reserve the need to back-seat drive here unless I could back it up with a comparable body of work.

http://www.theregister.co.uk/2012/03/07/amd_opteron_bug_drag...

You don't even need to do anything that hard. All you need to is run basic benchmarks and compare the results to what other filesystems can do, and when yours is about half as fast that should make you go "huh"...

Hammer is twice as fast, not half. So huh

So it'll now be 4x?

We need benchmarks, and this is the old version only.

Many problems have obvious solutions in hindsight.

Isn't NCQ meant to do this? I mean reorder the write commands into an optimal order.