1. 16 Jun, 2017 2 commits
  2. 02 Jun, 2017 1 commit
  3. 13 May, 2017 1 commit
  4. 12 May, 2017 1 commit
  5. 04 May, 2017 2 commits
  6. 21 Apr, 2017 1 commit
  7. 10 Apr, 2017 2 commits
  8. 06 Apr, 2017 1 commit
  9. 05 Apr, 2017 1 commit
  10. 04 Apr, 2017 1 commit
  11. 21 Mar, 2017 1 commit
  12. 17 Mar, 2017 1 commit
  13. 14 Mar, 2017 2 commits
  14. 23 Feb, 2017 1 commit
  15. 17 Feb, 2017 1 commit
  16. 27 Jan, 2017 3 commits
  17. 03 Jan, 2017 1 commit
  18. 20 Dec, 2016 1 commit
  19. 15 Dec, 2016 1 commit
  20. 02 Dec, 2016 1 commit
  21. 23 Nov, 2016 2 commits
    • Yorick Peterse's avatar
      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
      5371da34
    • Ahmad Sherif's avatar
      91633281
  22. 17 Nov, 2016 1 commit
  23. 14 Nov, 2016 1 commit
  24. 09 Nov, 2016 1 commit
  25. 28 Oct, 2016 1 commit
  26. 20 Oct, 2016 1 commit
  27. 19 Oct, 2016 2 commits
  28. 07 Oct, 2016 1 commit
  29. 20 Sep, 2016 4 commits
    • Timothy Andrew's avatar
      Use the `IssuableBaseService` lifecycle hooks to cache `MergeRequestsClosingIssues` · 68e1b5bb
      Timothy Andrew authored
      - Instead of overriding `create` and `update` in `MergeRequests::BaseService`
      - Get all merge request service specs passing
      68e1b5bb
    • Timothy Andrew's avatar
      Implement a second round of review comments from @DouweM. · 918e589c
      Timothy Andrew authored
      - Don't use `TableReferences` - using `.arel_table` is shorter!
      - Move some database-related code to `Gitlab::Database`
      - Remove the `MergeRequest#issues_closed` and
        `Issue#closed_by_merge_requests`  associations. They were either
        shadowing or were too similar to existing methods. They are not being
        used anywhere, so it's better to remove them to reduce confusion.
      - Use Rails 3-style validations
      - Index for `MergeRequest::Metrics#first_deployed_to_production_at`
      - Only include `CycleAnalyticsHelpers::TestGeneration` for specs that
        need it.
      - Other minor refactorings.
      918e589c
    • Timothy Andrew's avatar
      Implement (some) comments from @DouweM's review. · 71d4bf72
      Timothy Andrew authored
      - Move things common to `Issue` and `MergeRequest` into `Issuable`
      - Move more database-specific functions into `Gitlab::Database`
      - Indentation changes and other minor refactorings.
      71d4bf72
    • Timothy Andrew's avatar
      Implement review comments from @yorickpeterse · 8957293d
      Timothy Andrew authored
      1. Change multiple updates to a single `update_all`
      
      2. Use cascading deletes
      
      3. Extract an average function for the database median.
      
      4. Move database median to `lib/gitlab/database`
      
      5. Use `delete_all` instead of `destroy_all`
      
      6. Minor refactoring
      8957293d