
Previously the full map from review to marks was constructed, thus resulting in storing all marks records at peak. Now we use the fact that marks are ordered by time in runtime storage and if we observe marks for patch N it means that all from N-1 were seen before. Thus the maximum memory allocation is reviews count multiplied by number of marks in last patches (approximately by average number of patches less then before) Part of blueprint memory-optimizations Change-Id: Ia33001f57b0d92f6ff562f8c51aecba5875e8825
Stackalytics
Application Features
Stackalytics is a service that automatically analyzes OpenStack development activities and displays statistics on contribution. The features are: * Extraction of author information from git log, store it in the database; * Calculate metrics on number of lines changed (LOC) and commits; * Mapping authors to companies and launchpad ids; * Filter statistics by time, modules, companies, authors; * Extract blueprint and bug ids from commit messages; * Auto-update of database.
Project Info
- Web-site: http://stackalytics.com/
- Source Code: http://github.com/stackforge/stackalytics
- Wiki: https://wiki.openstack.org/wiki/Stackalytics
- Launchpad: https://launchpad.net/stackalytics
- Blueprints: https://blueprints.launchpad.net/stackalytics
- Bugs: https://bugs.launchpad.net/stackalytics
- Code Reviews: https://review.openstack.org/#q,status:open+stackalytics,n,z
- IRC: #openstack-stackalytics at freenode
Description
Languages
Python
61.6%
HTML
18.9%
JavaScript
12%
CSS
7.5%