Read about our upcoming Code of Conduct on this issue

  1. 27 Nov, 2018 1 commit
  2. 27 Jun, 2018 1 commit
  3. 21 Jun, 2018 1 commit
    • Yorick Peterse's avatar
      Don't expose project names in various counters · 76e4045a747c
      Yorick Peterse authored
      Various counters would expose either project names, or full project
      paths (e.g. "gitlab-org/gitlab-ce"). This commit changes various places
      where we use "add_event" so we no longer expose (potentially) private
      information.
      76e4045a747c
  4. 19 Jun, 2018 1 commit
  5. 12 Jun, 2018 1 commit
  6. 25 Apr, 2018 1 commit
  7. 03 Apr, 2018 1 commit
  8. 28 Mar, 2018 1 commit
  9. 15 Jan, 2018 1 commit
  10. 15 Dec, 2017 1 commit
  11. 05 Dec, 2017 1 commit
  12. 04 Dec, 2017 1 commit
  13. 10 Oct, 2017 1 commit
  14. 17 Aug, 2017 1 commit
  15. 05 Jun, 2017 1 commit
  16. 21 Oct, 2016 1 commit
    • Yorick Peterse's avatar
      Re-organize queues to use for Sidekiq · 02c0ae5ed1f6
      Yorick Peterse authored
      Dumping too many jobs in the same queue (e.g. the "default" queue) is a
      dangerous setup. Jobs that take a long time to process can effectively
      block any other work from being performed given there are enough of
      these jobs.
      
      Furthermore it becomes harder to monitor the jobs as a single queue
      could contain jobs for different workers. In such a setup the only
      reliable way of getting counts per job is to iterate over all jobs in a
      queue, which is a rather time consuming process.
      
      By using separate queues for various workers we have better control over
      throughput, we can add weight to queues, and we can monitor queues
      better. Some workers still use the same queue whenever their work is
      related. For example, the various CI pipeline workers use the same
      "pipeline" queue.
      
      This commit includes a Rails migration that moves Sidekiq jobs from the
      old queues to the new ones. This migration also takes care of doing the
      inverse if ever needed. This does require downtime as otherwise new jobs
      could be scheduled in the old queues after this migration completes.
      
      This commit also includes an RSpec test that blacklists the use of the
      "default" queue and ensures cron workers use the "cronjob" queue.
      
      Fixes gitlab-org/gitlab-ce#23370
      02c0ae5ed1f6
  17. 17 Aug, 2016 1 commit
    • Yorick Peterse's avatar
      Tracking of custom events · 8f655bf7dfb2
      Yorick Peterse authored
      GitLab Performance Monitoring is now able to track custom events not
      directly related to application performance. These events include the
      number of tags pushed, repositories created, builds registered, etc.
      
      The use of these events is to get a better overview of how a GitLab
      instance is used and how that may affect performance. For example, a
      large number of Git pushes may have a negative impact on the underlying
      storage engine.
      
      Events are stored in the "events" measurement and are not prefixed with
      "rails_" or "sidekiq_", this makes it easier to query events with the
      same name triggered from different parts of the application. All events
      being stored in the same measurement also makes it easier to downsample
      data.
      
      Currently the following events are tracked:
      
      * Creating repositories
      * Removing repositories
      * Changing the default branch of a repository
      * Pushing a new tag
      * Removing an existing tag
      * Pushing a commit (along with the branch being pushed to)
      * Pushing a new branch
      * Removing an existing branch
      * Importing a repository (along with the URL we're importing)
      * Forking a repository (along with the source/target path)
      * CI builds registered (and when no build could be found)
      * CI builds being updated
      * Rails and Sidekiq exceptions
      
      Fixes gitlab-org/gitlab-ce#13720
      8f655bf7dfb2
  18. 26 Jul, 2016 1 commit
  19. 30 Jun, 2016 1 commit
  20. 03 Jun, 2016 3 commits
  21. 19 Mar, 2016 1 commit
    • Yorick Peterse's avatar
      Cache output of Repository#exists? · 2c904501c8a2
      Yorick Peterse authored
      This caches the output of Repository#exists? in Redis while making sure
      it's flushed properly when creating new repositories, deleting them,
      etc.
      
      For the ProjectWiki tests to work I had to make ProjectWiki#create_repo!
      public as testing private methods in RSpec is a bit of a pain.
      2c904501c8a2
  22. 23 Feb, 2016 1 commit
  23. 17 Feb, 2016 1 commit
  24. 18 Nov, 2015 1 commit
  25. 11 Sep, 2015 1 commit