Hello!
I'm using hibernate 3.0.5 with oracle and "sequence" id generator. Everything works fine except one thing. Under heavy load (really heavy, many inserts, updates) i have sequence locking. Have to enable Oracle sequence cache to avoid this.
I see 3 possible id generation strategies in my case:
1) using "sequence" (just as i do now)
2) using "seqhilo" - never used it before, but many sources recommend it as very efficient solution. since i use jdbc tx manager and hibernate created connections (via c3p0 pool) see no problem with this one
3) id assigned by trigger from sequence with "assigned" generator
I wonder, which strategy is most performant?
Thank you
|