I've followed badger since it's beta and the discussions it emitted. Those
"lines" and discussions, alongside it's history, do not provide the most
happy influence that one would hope for.
On Sunday, January 21, 2018 at 7:51:52 PM UTC+3:30, Diego Medina wrote:
>
> The use of SyncWrites=false on
The use of SyncWrites=false on badger's benchmark was called out on reddit
and the benchmark author's reply was along the lines of "it's ok for our
use case to lose the last few [seconds|ms] of data"
You draw your conclusion on where you want to keep your data.
On Thursday, January 18, 2018
In docs for boltdb it is stated that NoSync should be used very carefully
because it can leave the database in an inconsistent state.
If a full fledged distributed database was the case, a no-sync manner would
be acceptable. But for an embedded database, it is not a plus (to be
performant in no
Are you using 'SyncWrites=false'? (Or 'NoSync' with boltdb?)
It looks like the badger benchmarks from github.com/dgraph-io/badger-bench
do not sync.
On Thursday, January 18, 2018 at 1:33:02 PM UTC-6, dc0d wrote:
>
> Badger write performance is a bit worse than boltdb. And badger suggests
> to
