On 2014-05-27 20:51, [email protected] wrote:
So what do you think.. something that could be improved here? H2 seems to spend most of its time in places like TreeCurson.next() and other index-related methods. Just a wild guess: maybe it is recalculating some index a million times (after every updated row update), instead of first doing all the updates and then recalculating the index just once..?
No, it's spending all of it's time deleting rows and checking that the deleted rows are not used by a referential constraint.
I would suggest figuring out which query is the problem child, and then doing an EXPLAIN PLAN on that query. You're probably missing an index somewhere and it's doing lots of table scans. -- 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. For more options, visit https://groups.google.com/d/optout.
