Gregory Farnum wrote:
On Fri, Oct 23, 2015 at 7:59 AM, Howard Chu <hyc@xxxxxxxxx> wrote:
If the stream of writes is large enough, you could omit fsync because
everything is being forced out of the cache to disk anyway. In that
scenario, the only thing that matters is that the writes get forced out in
the order you intended, so that an interruption or crash leaves you in a
known (or knowable) state vs unknown.
The RADOS storage semantics actually require that we know it's durable
on disk as well, unfortunately. But ordered writes would probably let
us batch up commit points in ways that are a lot friendlier for the
drives!
Ah, that's too bad. LMDB does fine with only ordering, but never mind.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
