1. 03 Mar, 2017 1 commit
  2. 23 Feb, 2017 5 commits
  3. 15 Feb, 2017 1 commit
  4. 02 Feb, 2017 1 commit
  5. 01 Feb, 2017 1 commit
  6. 31 Jan, 2017 8 commits
  7. 27 Jan, 2017 1 commit
  8. 18 Jan, 2017 1 commit
  9. 19 Dec, 2016 2 commits
  10. 17 Dec, 2016 2 commits
  11. 12 Dec, 2016 1 commit
  12. 11 Nov, 2016 1 commit
  13. 28 Oct, 2016 1 commit
  14. 10 Oct, 2016 1 commit
    • Yorick Peterse's avatar
      Precalculate trending projects · 8d729570767c
      Yorick Peterse authored
      This commit introduces a Sidekiq worker that precalculates the list of
      trending projects on a daily basis. The resulting set is stored in a
      database table that is then queried by Project.trending.
      
      This setup means that Unicorn workers no longer _may_ have to calculate
      the list of trending projects. Furthermore it supports filtering without
      any complex caching mechanisms.
      
      The data in the "trending_projects" table is inserted in the same order
      as the project ranking. This means that getting the projects in the
      correct order is simply a matter of:
      
          SELECT projects.*
          FROM projects
          INNER JOIN trending_projects ON trending_projects.project_id = projects.id
          ORDER BY trending_projects.id ASC;
      
      Such a query will only take a few milliseconds at most (as measured on
      GitLab.com), opposed to a few seconds for the query used for calculating
      the project ranks.
      
      The migration in this commit does not require downtime and takes care of
      populating an initial list of trending projects.
      8d729570767c
  15. 03 Oct, 2016 1 commit
  16. 07 Sep, 2016 2 commits
    • Olaf Tomalka's avatar
      Limited amount of pruned Event rows per run · a267dee7f44e
      Olaf Tomalka authored
      Old deployments of Gitlab might have a big number of old events to be
      deleted. Such numbers cause the worker to timeout.
      I've limited the amount of rows that should be destroyed at once to
      10000, and increased how often pruning shall take place to 4 times a
      day.
      a267dee7f44e
    • Olaf Tomalka's avatar
      Added cron to prune events older than 12 months. · 0ceb674afd60
      Olaf Tomalka authored
      Since contribution calendar shows only 12 months of activity,
      events older than that time are not visible anywhere and can be
      safely pruned saving big amount of database storage.
      
      Fixes #21164
      0ceb674afd60
  17. 25 Aug, 2016 1 commit
  18. 19 Aug, 2016 1 commit
  19. 18 Aug, 2016 1 commit
  20. 04 Aug, 2016 2 commits
  21. 26 Jul, 2016 1 commit
  22. 21 Jul, 2016 1 commit
  23. 18 Jul, 2016 1 commit
  24. 01 Jul, 2016 1 commit
  25. 30 Jun, 2016 1 commit