Slow Performance - Versioning everything in the system?

[csiege]

Hi,

I read the wiki note on how to set up the content model to automatically setup everything as versioning. (adding the versionable aspect as a mandatory aspect on cm:content)

Upon adding it and loading the system, I could see a gradual performance slow down on the ftp import speed.

I did some tests and see the following:

1 non versioned file results in
    1 Node table row and 6 Node_Properties table rows.

1 versioned file results in
     19 Node table rows and 33 Node_Properites rows.

The ftp seems to remain fast without versioning enabled by default.

Should I be concerned here?  Should we not proceed down the path of versioning everything?

thanks.

Chris

[derek]

Hi,

It is not the quantity of nodes or properties that will be causing the issue, but rather the structure of the nodes.

While the FTP would most likely be distributing documents around the repo, the versioning model is much more compact.  This will lead to a degradation in performance in V1.3, but has been fixed in V1.4.  In fact, the FTP performance is up for V1.4 (pulled in from a branch to HEAD yesterday).

I'll make a specific note to test the auto-versioning scalability and ensure that it is up to scratch (http://www.alfresco.org/jira/browse/AR-815).

Regards

[csiege]

From what I am seeing this is not limited to FTP, but is being exposed through the web client when operation of adding the versionable aspect is performed. 

Maybe a by product of the intial load using FTP?
Is that what you are saying?

What will happen if I proceed with 1.3.1?  Will an upgrade later to 1.4 fix whatever will already be loaded into the 1.3.1 version of my repo?

thanks.

Chris