prometheus/cmd/tsdb
Fabian Reinartz 6892fc6dcb Finish old WAL segment async, default to no fsync
We were still fsyncing while holding the write lock when we cut a new
segment. Given we cannot do anything but logging errors, we might just
as well complete segments asynchronously.

There's not realistic use case where one would fsync after every WAL
entry, thus make the default of a flush interval of 0 to never fsync
which is a much more likely use case.
2017-09-08 18:41:12 +02:00
..
.gitignore Add write benchmark utility 2016-12-07 17:30:10 +01:00
main.go Finish old WAL segment async, default to no fsync 2017-09-08 18:41:12 +02:00
Makefile Add mutex profiling to benchmark 2017-05-14 11:51:56 +02:00