1. 09 Jul, 2018 1 commit
  2. 28 Sep, 2017 2 commits
  3. 23 Jun, 2017 4 commits
  4. 07 Jun, 2017 1 commit
  5. 23 Nov, 2016 1 commit
    • 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:
  6. 30 Apr, 2015 1 commit
  7. 11 Dec, 2013 1 commit
  8. 02 Dec, 2013 1 commit