Thanks for this detailed answer. Have a good day On Fri, 14 Aug 2009 11:54:26 +0200, Andreas Hartmann <[email protected]> wrote: > Hi Florent, > > Florent André schrieb: >> Hi Andreas, hi all >> >> You said : >> >> On Wed, 12 Aug 2009 12:03:16 +0200, Andreas Hartmann <[email protected]> >> wrote: >>> IMO the only reason for storing multiple content items in a single >>> document is the limited scalability of the sitetree, but this should >>> only be noticeable when there are several 10.000 or 100.000 documents. >>> >> >> There is a not little difference between 10.000 and 100.000 documents... >> :) >> >> There is any information on the max number of document that can be deal ? > > I think the only hard limit is the amount of RAM that's available to the > JVM. There is a performance degradation when the sitetree is handled, > but I think it's pretty much linear. > > >> What kind of problems can occur (difficult copy/past, time to access, >> loss >> of data,...) ? > > Loss of data should not be an issue, since the complete sitetree is > locked in each transaction it is involved in. > > The most significant issue is the performance degradation. Because the > sitetree is stored in a single file and there is no session > synchronization mechanism, it has to be parsed after each change. So if > you have a large sitetree and someone inserts a document or changes a > navigation title, the next request will be slower. There is a single > sitetree object with some indexes for faster node lookup that is shared > by all read-only sessions, so when no changes are made the system should > be pretty fast even when there are lots of documents. Maybe someone > would like to run some benchmarks? > > If someone still uses the old navigation framework from the sitetree > module instead of the new navigation module, there will be a performance > degradation with large sitetrees. This should not be an issue with the > new navigation module. > >> When you say "there are several 10.000 or 100.000 documents", this is for >> each publication or for the all Lenya instance ? > > That's for each publication, or rather each area, since the sitetree is > stored per area. So you could mitigate the effects by distributing your > documents across multiple publication. I think it's possible to store > huge amounts of documents when you use many publications. > > -- Andreas
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
