BigW Consortium Gitlab

  1. 15 Feb, 2017 1 commit
  2. 31 Dec, 2016 1 commit
  3. 25 Nov, 2016 1 commit
  4. 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
  5. 07 Nov, 2016 1 commit
  6. 31 Aug, 2016 1 commit
  7. 20 Jul, 2016 1 commit
  8. 14 Jul, 2016 1 commit
  9. 28 Jun, 2016 1 commit
  10. 03 Jun, 2016 2 commits
  11. 02 Jun, 2016 1 commit
  12. 31 May, 2016 1 commit
  13. 26 May, 2016 1 commit
  14. 23 May, 2016 1 commit
  15. 16 May, 2016 1 commit
  16. 04 May, 2016 1 commit
  17. 01 May, 2016 1 commit
  18. 25 Apr, 2016 1 commit
  19. 31 Mar, 2016 2 commits
  20. 24 Mar, 2016 1 commit
  21. 20 Mar, 2016 1 commit
  22. 17 Mar, 2016 1 commit
  23. 11 Mar, 2016 2 commits
  24. 01 Mar, 2016 3 commits
  25. 04 Feb, 2016 1 commit
  26. 08 Jan, 2016 1 commit
  27. 03 Jan, 2016 1 commit
  28. 14 Oct, 2015 1 commit
  29. 15 Sep, 2015 2 commits
  30. 04 Sep, 2015 2 commits
  31. 03 Sep, 2015 3 commits