4 ms·

I've been using GitLab before, and use it from time-to-time still, but I've moved over to a self-hosted Gogs[0] server with Drone CI[1]. Both projects are activ

I've been using GitLab before, and use it from time-to-time still, but I've moved over to a self-hosted Gogs[0] server with Drone CI[1]. Both projects are actively maintained and both runs super well in Docker. Gogs is almost an identical clone of GitHub, although some small parts are missing but will most definitely be added in an upcoming version. Gogs is a lot more lightweight and faster than GitLab is. Our previous GitLab instance (7.X version range) used over 1.7GB of RAM (roughly 15 repos with 3 users) and always took longer than 1 second to serve a request (commit browsing was really bad, >5 seconds to serve such a request) while our Gogs installation uses 15MB and always serve requests sub-second. Both ran on the same hardware, with RAID10 SSDs. Definitely worth checking out if you want a self-hosted, lightweight & performant Git remote solution. Drone officially supports Gogs as well, so that's nice. [0] https://github.com/gogits/gogs/ https://github.com/gogits/gogs/ [1] https://github.com/drone/drone https://github.com/drone/drone

sytse 11y ago
Just wanted to add that we're working hard to bring down the request time in GitLab 8.x. We're not there yet but already optimized a lot of SQL queries and this release added support for better comment caching to prevent markdown parsing. Edit: we had to revert the comment caching at the last minute due to a bug but we're working on that, many other improvements and performance monitoring with InFluxDB and Grafana
- lhecker 11y ago
  I can definitely confirm that somewhere around the 8.0 release (I forgot when exactly) GitLab got a lot faster in general. Previously with the 7.x line it took about a couple seconds at least to load a page but now I barely get over a second until "onload", with response times of about 400ms. In general I wouldn't consider performance with GitLab an issue and denote it as a selling point for Gogs anymore - it would just be nice if it no longer felt like a Ruby on Rails website... A optimized site of mine with similiar complexity and database setup has a response time of 16ms and an "onload" event after about 400ms (using PHP-FPM 7 & MariaDB). ;)
  - sytse 11y ago
    Glad to hear performance got better in 8.x. What can we improve to make it feel better?
    - tiku 11y ago
      Less memory usage.. I went from gitlab to gogs because of that.. 2gb usage while idle..
      - sytse 11y ago
        Thanks, we're working towards a multithreaded application server to reduce memory usage https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 https://gitlab.com/gitlab-org/gitlab-ce/issues/3592
joejoebob 11y ago
Same here. Switching to Gogs saved several GB of memory, and it's much faster.

sytse 11y ago

Just wanted to add that we're working hard to bring down the request time in GitLab 8.x. We're not there yet but already optimized a lot of SQL queries and this release added support for better comment caching to prevent markdown parsing. Edit: we had to revert the comment caching at the last minute due to a bug but we're working on that, many other improvements and performance monitoring with InFluxDB and Grafana

lhecker 11y ago
I can definitely confirm that somewhere around the 8.0 release (I forgot when exactly) GitLab got a lot faster in general. Previously with the 7.x line it took about a couple seconds at least to load a page but now I barely get over a second until "onload", with response times of about 400ms. In general I wouldn't consider performance with GitLab an issue and denote it as a selling point for Gogs anymore - it would just be nice if it no longer felt like a Ruby on Rails website... A optimized site of mine with similiar complexity and database setup has a response time of 16ms and an "onload" event after about 400ms (using PHP-FPM 7 & MariaDB). ;)
- sytse 11y ago
  Glad to hear performance got better in 8.x. What can we improve to make it feel better?
  - tiku 11y ago
    Less memory usage.. I went from gitlab to gogs because of that.. 2gb usage while idle..
    - sytse 11y ago
      Thanks, we're working towards a multithreaded application server to reduce memory usage https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 https://gitlab.com/gitlab-org/gitlab-ce/issues/3592

joejoebob 11y ago

Same here. Switching to Gogs saved several GB of memory, and it's much faster.