Has Database.runInTransaction() any merit with ForestDB, performance-wise?

It makes sense to use transaction with Sqlite as it can save quite a lot of transactions. But ForestDB has by default no transactions, so performance-wise, the runInTransaction() is maybe unnecessary to be used with ForestDB? Just asking about performance here.

ForestDB has transactions.

Making a filesystem write durable involves expensive system calls that require blocking until data reaches the physical medium. If you don’t use transactions, that happens after each individual change. With a transaction, it happens only upon commit. Thus transactions greatly improve performance when you make many changes together.

Ah, in Linux it’s disk barriers? That makes sense. Thank you for reply, I’ll thus continue to use transactions.