BigW Consortium Gitlab

  1. 21 Mar, 2017 1 commit
  2. 24 Feb, 2017 1 commit
  3. 23 Feb, 2017 3 commits
  4. 13 Feb, 2017 4 commits
  5. 25 Nov, 2016 1 commit
  6. 23 Nov, 2016 1 commit
    • Remove event caching code · 5371da34
      Yorick Peterse authored
      Flushing the events cache worked by updating a recent number of rows in
      the "events" table. This has the result that on PostgreSQL a lot of dead
      tuples are produced on a regular basis. This in turn means that
      PostgreSQL will spend considerable amounts of time vacuuming this table.
      This in turn can lead to an increase of database load.
      
      For GitLab.com we measured the impact of not using events caching and
      found no measurable increase in response timings. Meanwhile not flushing
      the events cache lead to the "events" table having no more dead tuples
      as now rows are only inserted into this table.
      
      As a result of this we are hereby removing events caching as it does not
      appear to help and only increases database load.
      
      For more information see the following comment:
      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037
  7. 16 Nov, 2016 1 commit
  8. 09 Nov, 2016 1 commit
  9. 27 Oct, 2016 1 commit
  10. 20 Oct, 2016 2 commits
    • Differentiate the expire from leave event · f488b9f7
      Callum Dryden authored
      At the moment we cannot see weather a user left a project due to their
      membership expiring of if they themselves opted to leave the project.
      This adds a new event type that allows us to make this differentiation.
      Note that is not really feasable to go back and reliably fix up the
      previous events. As a result the events for previous expire removals
      will remain the same however events of this nature going forward will be
      correctly represented.
    • Differentiate the expire from leave event · 9124310f
      Callum Dryden authored
      At the moment we cannot see weather a user left a project due to their
      membership expiring of if they themselves opted to leave the project.
      This adds a new event type that allows us to make this differentiation.
      Note that is not really feasable to go back and reliably fix up the
      previous events. As a result the events for previous expire removals
      will remain the same however events of this nature going forward will be
      correctly represented.
  11. 11 Oct, 2016 1 commit
  12. 07 Oct, 2016 1 commit
    • Fix Event#reset_project_activity updates · 16626409
      Stan Hu authored
      !6678 removed the lease from Event#reset_project_activity, but it wasn't
      actually updating the project's last_activity_at timestamp properly.
      The WHERE clause would always return no matching projects. The spec
      passed occasionally because the created_at timestamp was automatically
      set to last_activity_at.
  13. 04 Oct, 2016 1 commit
    • Remove lease from Event#reset_project_activity · c9bcfc63
      Yorick Peterse authored
      Per GitLab.com's performance metrics this method could take up to 5
      seconds of wall time to complete, while only taking 1-2 milliseconds of
      CPU time. Removing the Redis lease in favour of conditional updates
      allows us to work around this.
      
      A slight drawback is that this allows for multiple threads/processes to
      try and update the same row. However, only a single thread/process will
      ever win since the UPDATE query uses a WHERE condition to only update
      rows that were not updated in the last hour.
      
      Fixes gitlab-org/gitlab-ce#22473
  14. 20 Sep, 2016 1 commit
  15. 19 Sep, 2016 1 commit
  16. 30 Aug, 2016 1 commit
  17. 06 Jul, 2016 1 commit
  18. 04 Jul, 2016 1 commit
  19. 28 Jun, 2016 1 commit
  20. 03 Jun, 2016 2 commits
  21. 16 May, 2016 5 commits
  22. 09 May, 2016 1 commit
    • Remove the annotate gem and delete old annotations · f1479b56
      Jeroen van Baarsen authored
      In 8278b763 the default behaviour of annotation
      has changes, which was causing a lot of noise in diffs. We decided in #17382
      that it is better to get rid of the whole annotate gem, and instead let people
      look at schema.rb for the columns in a table.
      
      Fixes: #17382
  23. 06 May, 2016 1 commit
  24. 25 Apr, 2016 1 commit
  25. 24 Mar, 2016 2 commits
  26. 17 Mar, 2016 1 commit
  27. 04 Feb, 2016 1 commit
  28. 27 Jan, 2016 1 commit
    • Use Atom update times of the first event · de7c9c7a
      Yorick Peterse authored
      By simply loading the first event from the already sorted set we save
      ourselves extra (slow) queries just to get the latest update timestamp.
      This removes the need for Event.latest_update_time and significantly
      reduces the time needed to build an Atom feed.
      
      Fixes gitlab-org/gitlab-ce#12415