topic Poor performance during document deletion in Alfresco Archive

Poor performance during document deletion

fschnell — Mon, 16 Apr 2007 21:10:30 GMT

A colleague of mine (who also wrote this article) did some trials on our out-of-the-box Alfresco 2.0 community with MySQL on OpenSuse to see how long it would take to copy and paste a complex file structure from drive to drive. The file structure chosen consisted of 296 files within 29 folders, a to

Re: Poor performance during document deletion

derek — Tue, 17 Apr 2007 09:44:15 GMT

Hi,

Files and folders are, by default, archived. So the delete is not only moving the nodes, but is ensuring that all association to and from the nodes are archived as well. This is an expensive process, but can be switched off in the model.

If it is off, then the process still has to walk the tree to delete the nodes. The reason why we don't do this in the background is that it is possible that the delete actually violates some integrity constraint and should therefore be disallowed. Each node in the tree has to be evaluated to against the model constraints.

There are solutions to these problems, ofcourse. We could preserve associations to deleted nodes and avoid displaying them in the clients, for instance. This would allow us to just move and archive the top-level node. Complete deletion can do something similar.

Regards

Re: Poor performance during document deletion

derek — Tue, 17 Apr 2007 09:50:22 GMT

Could you repeat the same tests using the latest code on from our SVN? With such a long-running transaction, you'll need the support to keep the memory sizes in check.

Regards