Default to DB_TXN_WRITE_NOSYNC for all transactional operations #1360

1. 
   jgarzik commented at 5:27 am on May 19, 2012: contributor

   • This is safer than DB_TXN_NOSYNC, and does not appear to impact performance.
   • Applying this to the dbenv is necessary to avoid many fdatasync(2) calls on db 5.x
   • We carefully and thoroughly flush databases upon shutdown and other important events already.
2. Default to DB_TXN_WRITE_NOSYNC for all transactional operations

   * This is safer than DB_TXN_NOSYNC, and does not appear to impact
     performance.
   * Applying this to the dbenv is necessary to avoid many fdatasync(2)
     calls on db 5.x
   * We carefully and thoroughly flush databases upon shutdown and
     other important events already.

   394b9298fa
3. 
   gavinandresen commented at 1:27 pm on May 19, 2012: contributor

   ACK
4. 
   sipa commented at 3:02 pm on May 19, 2012: member

   No noticeable improvement here (bdb 5.1), but ACK.
5. jgarzik referenced this in commit cde87ee75c on May 19, 2012
6. jgarzik merged this on May 19, 2012
7. jgarzik closed this on May 19, 2012

   ---

8. coblee referenced this in commit c9be7437bf on Jul 17, 2012
9. suprnurd referenced this in commit 0bc6d92334 on Dec 5, 2017
10. lateminer referenced this in commit 905d04b2c6 on Jan 22, 2019
11. lateminer referenced this in commit aee230135f on May 6, 2020
12. DrahtBot locked this on Sep 8, 2021

Contributors
jgarzik gavinandresen sipa