On Mon, Jul 21, 2008 at 11:20 AM, zhonglf <[EMAIL PROTECTED]> wrote: > > > > Stefan Guggisberg-2 wrote: >> >> jackrabbit is not optimized for very flat node hierarchies (e.g. with more >> than >> 30k child nodes per node). if you create a deeper structure you'll >> experience a >> lot better performance. >> >> anyway, your figures seem to be *very* high (200s for 1k nodes)... >> are you using any of the foillowing? >> - references >> - versioning >> - large binaries >> >> cheers >> stefan >> >> > > yes, all of them. Is this the reason?
probably yes. performance WRT large binaries should be significantly improved by using the DataStore. referential integrity and versioning are very powerful features but they come at a certain cost. make sure you're only using them where needed. other factors that might have a great impact on performance is the choice of persistence manager and backend. bunde db persistence manager in combination with embedded derby currently gets you the best performance. if you change the persistence manager configuration make sure modify the workspace.xml as well and not just the repository.xml. cheers stefan > > > -- > View this message in context: > http://www.nabble.com/Too-slow---adding-1%2C000-node-into-the-repositroy-tp18525321p18564929.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > >
