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
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
] [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2003 12:44 PM
To: OJB Users List
Subject: Re: ODMG vs. PB
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
