- **status**: review --> closed - **Reviewer**: Dave Brondsema - **Comment**:
Thanks. I also did some measurements of a few SVN imports. Optimizing for SVN imports is of particular desire for me and how we're using Allura. An import & refresh will fully populate `repo_ci` and `repo_diffinfo` collections. Other collections (`repo_trees`, `repo_tree`, `repo_last_commit`) will populate as the repo is browsed. The sizes of the collections, after browsing around a fair bit (wget spidering), are the same order of magnitude between `repo_ci`, `repo_diffinfo`, `repo_tree`, and `repo_last_commit`. Good targets to address first would be `repo_ci` and`repo_diffinfo` since they are created at immediately during "refresh". Next could be `repo_tree`. Not sure about tackling `repo_last_commit` since the logic is very complex and caching is necessary since it is expensive calculations. --- ** [tickets:#7828] Analyze & document usage of repo collections** **Status:** closed **Milestone:** unreleased **Labels:** 42cc sf-current sf-2 indexless **Created:** Mon Feb 09, 2015 04:13 PM UTC by Dave Brondsema **Last Updated:** Wed Feb 18, 2015 10:41 AM UTC **Owner:** Igor Bondarenko 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.
