That smells like some kind of linux filesystem issue.
Some of the linux filesystems can take a very long time to perform a
sync() operation, which is what H2 performs during a commit to make sure
the data gets to disk.
I would start by looking at what options you are using when mounting
your filesystem, and then having a look around for articles about how
your filesystem performs sync() operations.
On 2013-04-08 18:16, Klausen Schaefersinho wrote:
Hi,
we are using H2 for an OSGI application. Under linux and windows on an
X86 the database performs very well. However when running on an ARM
based system (raspberry pi) with flash memory (sd-card) the database
inserts get terrible slow. Updating an exiting object (should string
fields) takes 6 seconds! We are using eclipselink and the delay occurs
during the commit of the JPA transaction.
We first thought it's an IO problem so we used a faster SD-card but
that didn't change anything. We have also tried Postgres instead and
it worked well (~70ms), but we would like to continue using H2.
Anybody has an idea why this happens?
THX,
Klaus
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
