It's beacuse ODMG is a full fledged Object transaction manager. It does a full tracking of object states during transactions etc.
This causes all the overhead. The "real" persistence work is done with the underlying PB API and is not slower than native PB operations.
cheers, Thomas
Jacob Hookom wrote:
Looking at the performance benchmarks at OJB's page, there's a dramatic difference in speed between ODMG and PB implementations. Is this because of the object locking features with ODMG, or is it because ODMG uses PB and that extra adapter layer causes slow downs?
-Jacob
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
