java - JPA and Derby Performance -

i wrote application using jpa. application makes around 5 or 6 inserts per second on 1 table. insert done simple transaction begin, persist , transaction commit.

with approach application has heavy cpu load (around 80%). using jvisualvm profiled application , came result:

this shows around 30% percent of time spent in writing , flushing log files. setexclusive method has load of 14% of time.

is there way optimize this? maybe disabling logging?

enterbios right. disable logging , don’t have database anymore, sql writing files (bye bye acid). databases do, derby uses group commit, i.e. log multiple transactions grouped in single disk write. if single update, commit, wait , insert the group commit have little effect there log single insert write.

the setexclusive time points contention same data (multiple threads accessing same database page).