Files @ 3ed43530d3b8
Branch filter:

Location: kallithea/docs/usage/statistics.rst - annotation

3ed43530d3b8 1.2 KiB text/prs.fallenstein.rst Show Source Show as Raw Download as Raw
Søren Løvborg
db: upgrade to SQLAlchemy 1.1, fixing invalid PostgreSQL SQL in User.is_default_user

eea19c23b741 triggered a bug in SQLAlchemy 1.0.17, causing invalid SQL to be
emitted for PostgreSQL: For the (Python) query '(x == y) == z', SQLAlchemy
generates the SQL 'x = y = z'. SQLite and MySQL accepts this, but PostgreSQL
does not. This bug has been fixed in 1.1.

Testing and review shows no problems with 1.1
.. _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.