You are viewing limited content. For full access, please sign in.

Question

Overhead of version tracking

Laserfiche Version 10

Updated March 4, 2016

asked on February 10, 2016

How much overhead is there in using version tracking? We only need version tracking turned on for a hand full of documents but it is very important to have it on for those documents and our users (including myself) often forget to turn it on. So I am considering turning on version tracking for the entire repository. How much overhead is there for doing this? Is there performance ramifications anywhere in Laserfiche? Most documents are not modified once stored in the repository. Is there still extra space used if there is only one version of the document?

0 0

Replies

replied on February 10, 2016

As far as i know version tracking is not much of an overhead as new versions are stored as delta's (difference of saved file and modified file). Deltas don't take much space and there is no extra processing required as they are bunch of files.

1 0

replied on March 4, 2016

This is partly true. The components of the document that didn't change at all are not saved, but deltas are not computed on the ones that did change. That is, if the user makes an edit to a Word document, both the before and the after are stored as complete Word documents, no matter how small the change was.

It is correct that merely turning on version control for a document does not add any overhead.

1 0

You are not allowed to follow up in this post.

Sign in to reply to this post.

Asked February 10, 2016
Updated March 4, 2016
86 views