I think it means that is why it doesn't sync for every commit, so it can
get higher performance than that.
If it syncs for every commit, then if you are committing each row and
doing a lot of updates for example, then you get bad performance.
Probably wouldn't matter much for an SSD, but on a rotational HDD it
makes a huge difference.
Anyway, yes H2 will get a lot more than 60 write operations per second.
Ryan
On 11/09/2014 4:21 PM, Anders wrote:
Hi,
/"According to documentation, the system doesn't call
FileDescriptor.sync () nor FileChannel.force () nor fsync
<http://en.wikipedia.org/wiki/Sync_%28Unix%29> for every commit
because they significantly degrade system performance: *only 60 write
operations per second <http://en.wikipedia.org/wiki/IOPS> are
achievable*."/ -- http://en.wikipedia.org/wiki/H2_%28DBMS%29
Could someone please confirm if this really is correct?
I will remember that H2 can perform so much better than this.
Thanks!
--
You received this message because you are subscribed to the Google
Groups "H2 Database" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to h2-database+unsubscr...@googlegroups.com
<mailto:h2-database+unsubscr...@googlegroups.com>.
To post to this group, send email to h2-database@googlegroups.com
<mailto:h2-database@googlegroups.com>.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
