This project is mirrored from https://gitlab.com/gitlab-org/gitlab-ce.git. Updated .
  1. 19 Aug, 2019 1 commit
  2. 12 Aug, 2019 3 commits
  3. 05 Apr, 2019 1 commit
  4. 24 Jan, 2019 1 commit
  5. 28 Nov, 2018 1 commit
  6. 23 Mar, 2018 1 commit
  7. 07 Feb, 2018 2 commits
    • Lin Jen-Shin's avatar
      Release the entire env · 31f1ec59
      Lin Jen-Shin authored
      31f1ec59
    • Lin Jen-Shin's avatar
      Try not to hold env and release the controller · d4d564c8
      Lin Jen-Shin authored
      after the request. This way, we could release the
      project referred from the controller, which potentially
      referred a repository which potentially allocated a lot of
      memories.
      
      Before this change, we could hold the last request data
      and cannot release the memory. After this change, the
      largest request data should be able to be collected from GC.
      
      This might not impact the instances having heavy load,
      as the last request should be changing all the time,
      and GC won't kick in for each request anyway.
      
      However it could still potentially allow us to free more
      memories for each GC runs, because now we could free one
      more request anyway.
      d4d564c8
  8. 28 Dec, 2017 1 commit
    • Lin Jen-Shin's avatar
      Warm up the app so it's fast for the 1st request · e202fe8c
      Lin Jen-Shin authored
      This would make the application considered ready much slower,
      but when it's ready, then it's really ready. Before this change,
      it claims to be ready, but it's annoyingly slow for the first
      request with GDK. It's 100% 502 for me, for the first request.
      
      This shouldn't really affect production or so, because if it's
      really ready, it should be blazingly fast, and it should not
      slow things down too much.
      
      The culprit here is probably `ActionController::Base.helpers.asset_path`
      but this could make sure that anything else would load first, too.
      e202fe8c
  9. 15 Jun, 2017 1 commit
  10. 02 Jun, 2017 6 commits
  11. 20 Jan, 2016 2 commits
  12. 28 May, 2015 1 commit
  13. 23 Jan, 2014 1 commit
    • Damjan Georgievski's avatar
      Check specifically for Unicorn in rack config.ru file · be150fa9
      Damjan Georgievski authored
      Don't assume that if the Rack server is not Passenger then it must be Unicorn. There are many other Rack servers in the world (uwsgi being one example that people use a lot).
      
      The reverse check is much more logical, i.e. check explicitly for Unicorn
      be150fa9
  14. 22 Dec, 2013 1 commit
  15. 20 Dec, 2013 1 commit
  16. 18 Dec, 2013 1 commit
  17. 28 Dec, 2012 1 commit
  18. 13 Oct, 2011 2 commits
  19. 08 Oct, 2011 1 commit