Skip to content

Instantly share code, notes, and snippets.

View HZ89's full-sized avatar

HarrisonZhu HZ89

  • tencent
  • China
  • 22:17 (UTC +08:00)
View GitHub Profile

Keybase proof

I hereby claim:

  • I am hz89 on github.
  • I am harrisonzhu (https://keybase.io/harrisonzhu) on keybase.
  • I have a public key ASArzT30wK2og_DO2gPwvRS6cS3wE066vNpWxA9PV4OTQgo

To claim this, I am signing this object:

@HZ89
HZ89 / gitlab.conf
Created September 29, 2016 07:46 — forked from sameersbn/gitlab.conf
Nginx reverse proxy configuration for GitLab
upstream gitlab {
server 172.17.42.1:10080 fail_timeout=0;
}
# let gitlab deal with the redirection
server {
listen 80;
server_name git.example.com;
server_tokens off;
root /dev/null;

Nginx Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400,000 to 500,000 requests per second (clustered), most what i saw is 50,000 to 80,000 (non-clustered) requests per second and 30% CPU load, course, this was 2xIntel Xeon with HT enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

First, you will need to install nginx, my way to install nginx is compiling it from source, but for now we will use apt-get