Hi, > don't believe that FSYNC usage (on db files / on transaction > log / on commit / on timer ) must to be a user selectable setup ?
It should be, for those cases where performance is more important than reliability (import, test). Except, if performance is not affected by fsync. Which I thought was the case, because fsync is only called on checkpoint and when closing the database, both shouldn't be very common operations except maybe when running the automated H2 tests. But if it really make a difference even if the database is not opened / closed very quickly in a loop. If somebody has a test case where performance is affected a lot by fsync please let me know. Maybe it's a problem I didn't know about. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
