My thought was that the large page size might be contributing to lock escalation so that the whole table was getting locked per insert or something, but I confess I don't know how derby handles that.
I will dig into some of the locking diagnostics. Thanks! - DAP On Feb 2, 2010, at 10:53 AM, Bryan Pendleton wrote: > David Parker wrote: >> slowdowns that we have traced to this insert - a single insert taking >> several seconds > > That feels more like a locking issue than an I/O issue, to me. > > Perhaps you have some sort of rarely-run query which, when it runs, > scans and processes the entire table, thus locking the table and > preventing any insert into the table. > > Just a guess. > > thanks, > > bryan > > > ============================================= David Parker [email protected]
