jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "Performance" by AlexanderKlimetschek
Date Mon, 12 Jan 2009 14:06:09 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by AlexanderKlimetschek:
http://wiki.apache.org/jackrabbit/Performance

The comment on the change is:
added info that the 10k limit is not JCR specific

------------------------------------------------------------------------------
  
  == Q. I have too many child nodes and performance goes down. ==
  
- A. The current Jackrabbit design is optimized for small to medium sized child node sets,
i.e. up to ~10k child nodes per node. Really large child node sets negatively affect write
performance (in the current design).
+ A. The current internal Jackrabbit design is optimized for small to medium sized child node
sets, i.e. up to ~10k child nodes per node. Really large child node sets negatively affect
write performance.
  
- Each node contain the references to all its child nodes. This is a design decision inside
Jackrabbit to improve speed when using few child nodes. To improve performance, introduce
some extra-levels to you content model. This also helps humans to explore the repository when
using a browser tool. Typical solutions are to use some categories of the context of your
data or date folders, such as "2009/01/09".
+ Please note that this is not a general issue of JCR but specific to Jackrabbit's current
internal persistence strategy - independent from the fact if you use a normal persistence
manager or a "bundle" persistence manager, albeit the latter one is recommended; see PersistenceManagerFAQ.
Each node contains the references to all its child nodes. This is a design decision inside
Jackrabbit to improve speed when using few child nodes. To improve performance, introduce
some extra-levels to your content model. This also helps humans to explore the repository
when using a browser tool. Typical solutions are to use some categories of the context of
your data or date folders, such as "2009/01/09".
  
  == Q. I have many references to a single node and performance goes down. ==
  

Mime
View raw message