The J2EENodeStore was send to this list by Ashok! Ashok's last commitment was posted on this list on February 3 2003!
I am using slide webdav/deltav interface and I have not seen any problems with adding a resource to the history (using checkin). But I intend to do some testing with versioning on 500.000 mill and 1 mill files using the setup as I described. The problems that I have seen so far is when moving or copying large collection on the server! /Jacob -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Martin Holz Sent: 20. juni 2003 17:41 To: [EMAIL PROTECTED] Subject: Re: Version control and performance "Jacob Lund" <[EMAIL PROTECTED]> writes: > Hi Martin! > > I am using the J2EENodeStore with 50.000 files in 9.000 collections. > All files have been placed under version control. It is running > without any problems and there is no decrease in speed compared to a > store with 100 files. > > I have had 500.000+ files in the store but without placing all the > files under version control. This was not a problem. This sounds good. But what do you mean by J2EENodeStore? There is a src/stores/slidestore/j2ee/J2EEDescriptorsStore.java. I can't see anything in it, which would change the linear behaviour. The performance of my server is also okay as long as standard operations like PUT and GET are involved. Do you use Webdav/DeltaV versioning or raw slide versioning? Raw slide should be okay too. Trouble starts, when a new Webdav version history is created, because all version histories are created in the same collection and as slide performance to store a node scales linear with the number of children the node has. Martin --------------------------------------------------------------------- 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]
