News for hackers. Stuff that matters.

A comment on MongoDB's Write Lock. Parent comment

Re:MongoDB's Write Lock by nknight on Saturday December 31, 2011 @06:59PM (#3412253)
> queued up on disk IO

And there's where your legacy understanding fails. You're really not supposed to be doing a lot of disk IO in modern datastores in the first place. Your working set should be in RAM.

> beat benchmarks

If my vendor is investing time in beating benchmarks instead of solving real problems, I'm finding a new vendor.

[ Parent | on HN ]
Re:MongoDB's Write Lock by eternalban on Saturday December 31, 2011 @09:15PM (#3412453)
"solving real problems"

I am not at all addressing MongoDB here to be clear -- just your comment regarding worthwhile "problems" to "solve".

It is not too difficult to foresee a future where energy costs will trump all other considerations, including development time, sys ops, etc. Specially for <X>aaS efforts, energy efficiency can clearly end up being a competitive edge.

[ Parent | on HN ]