Mercurial > kallithea
view docs/usage/statistics.rst @ 7464:12455b1a1a6f
front-end: Use select2 from node_modules and stop bundling it
select2 3.5.4 was added in 304e83e9bcde ... but the latest npm release in the 3
series is 3.5.1, so we use that one instead. We should probably upgrade to the
4 series.
The select2 images were not in the location the generated css pointed - now we
copy them from node_modules to the right location, next to the generated css.
Note: this will drop 190cb30841de "branches: fix performance of branch
selectors with many branches - only show the first 200 results" ... but it
should no longer be relevant now when we use server side filtering.
15e507047bae introduced select2-bootstrap.css - it is not clear what version
was used, but we use the latest 1.4.6 which also is very old.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Tue, 11 Dec 2018 01:22:56 +0100 |
parents | 5ae8e644aa88 |
children |
line wrap: on
line source
.. _statistics: ===================== Repository statistics ===================== Kallithea has a *repository statistics* feature, disabled by default. When enabled, the amount of commits per committer is visualized in a timeline. This feature can be enabled using the ``Enable statistics`` checkbox on the repository ``Settings`` page. The statistics system makes heavy demands on the server resources, so in order to keep a balance between usability and performance, statistics are cached inside the database and gathered incrementally. When Celery is disabled: On each first visit to the summary page a set of 250 commits are parsed and added to the statistics cache. This incremental gathering also happens on each visit to the statistics page, until all commits are fetched. Statistics are kept cached until additional commits are added to the repository. In such a case Kallithea will only fetch the new commits when updating its statistics cache. When Celery is enabled: On the first visit to the summary page, Kallithea will create tasks that will execute on Celery workers. These tasks will gather all of the statistics until all commits are parsed. Each task parses 250 commits, then launches a new task.