You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Jacob Hookom <ho...@uwec.edu> on 2003/04/03 20:54:16 UTC
ODMG vs. PB
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
RE: ODMG vs. PB
Posted by Gary Eberhart <ge...@cmcflex.com>.
I use both the PB and ODMG in the same accessor class. I use PB to do all
the read only processing and then ODMG when I will be updating or adding to
the database. I've only done a small bit of testing using this methodology
however.
cheers,
gary
-----Original Message-----
From: thma32@web.de [mailto:thma32@web.de]
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 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: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org
Re: ODMG vs. PB
Posted by Thomas Mahler <th...@web.de>.
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: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>