It relies on the JDO reference implementation, which breaks proxies. It works, is compliant, and is performant if you don't want any proxies, but this usually leads to some nasty memory issues.
On a performance note, the PB has the highest performance numbers as it doesn't do things like automatic dirtying. if you go to ODMG or OTM you get a bit larger performance hit.
On the other hand, if you always use OJB, or something else that can participate in the cache -- allowing you to cache aggressively, you will typically see a massive performance boost as OJB makes caching much easier than using raw jdbc.
My favorite example of this is an app we have which presently makes an obscene number of calls to the database for a couple of page loads. If we swap out to OJB using the default cache we can reduce it to 0 database hits per typical page load as it is frequently used and infrequently modified data -- prime for caching but from so many different tables that JDBC caching is really had to do for it.
-Brian
On May 4, 2004, at 7:29 AM, mirko wrote:
Reinhard Poetz wrote:OJB has a performance test suite.
Robert posted results here: http://marc.theaimsgroup.com/?l=ojb-dev&m=108208175512540&w=2
Thanks. I'd like to use JDO api but it wasn't in the test results. If its performance is like the PB's I could accept it.
Regards, mirko
--------------------------------------------------------------------- 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]
