Hi, For performance reasons, our client was doing the following for a large > insert: a constraint was being removed, insert the data, then constraint > added again.
I wonder if disabling and then re-adding the constraint really improved performance, if it caused an index to be created / dropped. I would think recovery is as fast / as slow as the time it took while the program was running. On recovery, these steps were being repeated many times when replaying the > transaction log. The startup was taking over 11 minutes on a small CPU. We > are changing the client to not need the constraint and therefore not add > and remove it. Now, the recovery time is much better. > OK. > But, I'm still looking at ways (h2 options or best practices) to keep the > recovery time as low as possible after power failure. > I would try to avoid adding / creating the same index over and over again at runtime (but this isn't really related to recovery). To speed up recovery, using a smaller log size might help (max_log_size). 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.
