Certainly, locking sequence cannot create the problems with performance, but a small improving it is not bad too, I guess. I have made tests, and you are right, to make changes does not make sense. In the synthetic tests ReentrantReadWriteLock shows better performance, but not in the org.h2.schema.Sequence.
I have yet one question, why in the org.h2.schema.Sequence update of increment field does not synchronized? On Oct 10, 8:09 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > Do you think it would improve performance, or why do you suggest to change > it? If yes, do you have any numbers on how much would it improve? What is > your use case? > > If performance is really a problem, possibly it would make sense to use > AtomicLong. > > Regards, > Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
