We will need richer criteria than simply age.  Consider a package that
didn't change in the last year -- purging it would provide little gain
while seriously limiting the repository's ability to do its SCM duty
(compare, merge, revert, etc. with prior versions).

Before we knee-jerk react by hacking down our persistent model just to
accomodate MC's unsustainable design, may we first at least consider
to upgrade MC to be more scalable?

For example, one of the things that is "slow" is due to merely
applying the underlining and highlighting in the Versions browser.
One thing that can be done here is quit going back all versions and
instead just the prior 20 or so...




On Wed, May 23, 2012 at 12:28 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> Accessing the repository gets slower and slower due to the ever increasing number of versions there.
>
> To make it faster we could remove old package versions. Say, everything older than a year (but keep at least one version of each package). We could move those to an "attic" repository.
>
> Sounds good? Other ideas?
>
> - Bert -
>
>