<s​yntheticbird:monero.social> hello

<s​yntheticbird:monero.social> hyc are you there?

<s​yntheticbird:monero.social> sorry for the offtopic and plunge you into nostalgia but during latest Cuprate meeting we were wondering why you used both NO_SYNC and MAP_ASYNC together here: github.com/monero-project/monero/bl…lockchain_db/lmdb/db_lmdb.cpp#L1444

<s​yntheticbird:monero.social> from lmdb documentation we mainly understood that were trying to change the same behavior. So we are unsure of what combining the two actually do. Is one overloading the other on specific platform ?

I took a quick glance over the mdb.c code, and it seems that MDB_NOSYNC takes precendence and if it's set, MDB_MAPASYNC does nothing

<s​yntheticbird:monero.social> thx sech1

although, if a sync is forced, MDB_MAPASYNC flag will be used

so it matters only when calling mdb_env_sync with force != 0

MDB_NOSYNC|MDB_MAPASYNC result in no syncs, unless you explicitly call mdb_env_sync(env, 1); - then it will use async flushes to disk

all that is based just on me reading the code, but you need to test it

<s​yntheticbird:monero.social> got it, thx again

<s​yntheticbird:monero.social> btw cuprate channel is on irc if you want

<s​yntheticbird:monero.social> I think i never saw you wandered in #cuprate

I joined it today

<s​yntheticbird:monero.social> lets go