You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by Jason Tesser <ja...@dotmarketing.com> on 2007/11/15 16:49:38 UTC

DBBundle or JNDIPersistenceManager

I am trying to figure out exactly what the differences are between the
BundlePersistenceManager and the Simple specifical the JNDI one.

Is there really a big performance difference between the two?

I also noticed that Postgres isn't in 1.3 Is there a reason for this?  Can
it be backported?

Thanks,
Jason

Re: DBBundle or JNDIPersistenceManager

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

On Nov 15, 2007 5:49 PM, Jason Tesser <ja...@dotmarketing.com> wrote:
> I am trying to figure out exactly what the differences are between the
> BundlePersistenceManager and the Simple specifical the JNDI one.

The bundle persistence managers store content in a more efficient way
than the older database persistence managers.

> Is there really a big performance difference between the two?

Depends on your access patterns, but for some cases the performance
improvement with bundle persistence managers can be quite dramatic.
The difference is caused by the fact that older database persistence
managers use a separate SELECT for each node and property, whereas the
bundle persistence managers retrieve a node and all it's properties in
a single SELECT statement.

> I also noticed that Postgres isn't in 1.3 Is there a reason for this?  Can
> it be backported?

Postgres support for bundle persistence was contributed (see
https://issues.apache.org/jira/browse/JCR-889) only after the 1.3
release branch was started, so it didn't make it in the release.

You should be able to backport the feature manually to a 1.3.x
release, but officially the feature will be available in the
Jackrabbit 1.4 release, due out by the end of this year.

BR,

Jukka Zitting