---
** [tickets:#7828] Analyze & document usage of repo collections**
**Status:** open
**Milestone:** unreleased
**Labels:** indexless sf-current
**Created:** Mon Feb 09, 2015 04:13 PM UTC by Dave Brondsema
**Last Updated:** Mon Feb 09, 2015 04:13 PM UTC
**Owner:** nobody
We've done some work in the past for our SCM repos to be "indexless", that is
use the git/hg/svn repo directly instead of indexing in mongo and using that.
(Storing in mongo can take up a lot of space and also adds delay for the
indexing process to run)
Analyze where each of the following collections (models) is used. Perhaps
cross-reference by page or function (e.g. browse repo, view commit, etc; also
git/svn/hg). Then we can plan which pages' functionality needs to be updated
to be able to remove them.
Collections (with relative size factors based on sf.net data):
* repo_trees (4x)
* repo_tree (2x)
* repo_last_commit (2x)
* repo_diffinfo (1x)
* repo_ci (very tiny)
* repo_commitrun (very tiny)
---
Sent from forge-allura.apache.org because [email protected] is subscribed
to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
