GitLab

Created by: btate

I have gitlab 4.1 running and the web interface runs fine after it's first started, but slows down significantly and starts timing out after a few days. If I restart it, it's back to normal. Anybody else seeing this?

Created by: Wijnand

Yes, + 1

By Administrator on 2013-02-05T11:39:41 (imported from GitLab project)

Created by: btate

I'm still having this issue with 4.2. Will 5.0 address this?

By Administrator on 2013-03-11T13:43:11 (imported from GitLab project)

Created by: dzaporozhets

Are you sure gitlab process are reason of slow performance?

By Administrator on 2013-03-11T13:46:22 (imported from GitLab project)

Created by: dzaporozhets

sidekiq or unicorn?

By Administrator on 2013-03-11T13:46:40 (imported from GitLab project)

Created by: btate

After a while it stops loading the web front end. The git backend works fine for pushes/pulls. But the web gives me a 504 gateway timeout. If I restart gitlab it works fine for a few hours, then does it again. Both sidkiq and unicorn are running I believe.

By Administrator on 2013-03-11T13:48:51 (imported from GitLab project)

Created by: dzaporozhets

Check if:

• some if some process eat all ram or cpu
• you have enough hdd space

By Administrator on 2013-03-11T13:58:26 (imported from GitLab project)

Created by: btate

The server I have this on has 2GB ram. I would assume that would be sufficient, but not ruling that out as the problem. What do you guys recommend?

The server says I have about 17GB available.

By Administrator on 2013-03-11T14:00:47 (imported from GitLab project)

Created by: dzaporozhets

2GB RAM its pretty enough. I recommend you to monitor processes when experience issue. check if unicorn worker dies.

By Administrator on 2013-03-11T14:05:02 (imported from GitLab project)

Created by: btate

How do I check if the unicorn work dies? Doesn't say anything in the unicorn error log about one dying.

By Administrator on 2013-03-11T14:21:22 (imported from GitLab project)

Created by: btate

Using top I have a lot of different gitlab processes running

5408 gitlab 20 0 901m 114m 7396 S 2.3 5.9 201:07.83 ruby
26248 gitlab 20 0 902m 113m 2408 S 5.0 5.8 2537:50 ruby
10920 gitlab 20 0 902m 112m 2408 S 5.0 5.8 2268:51 ruby
12726 gitlab 20 0 915m 112m 3772 S 0.0 5.7 1:27.08 ruby
12723 gitlab 20 0 921m 112m 4380 S 0.0 5.7 0:56.08 ruby
12502 gitlab 20 0 835m 104m 7292 S 0.0 5.3 0:19.50 ruby
16957 gitlab 20 0 838m 97m 2520 S 0.0 5.0 92:17.81 ruby

Which is causing not a lot of free memory Mem: 2008684k total, 1987548k used, 21136k free, 121940k buffers

By Administrator on 2013-03-11T14:25:55 (imported from GitLab project)

Created by: btate

Just noticed tomcat running in the background for some reason. Killed that process and the speed increased significantly. I'll continue posting any changes.

By Administrator on 2013-03-12T14:25:05 (imported from GitLab project)

Created by: senny

Is this still a problem?

By Administrator on 2013-05-06T10:40:15 (imported from GitLab project)

Created by: btate

Yeah. I'm still seeing this after a few days of being up. But I haven't been able to update to 5.0 yet. So that might solve something.

Thanks, Brandon

On May 6, 2013, at 6:40 AM, Yves Senn notifications@github.com wrote:

Is this still a problem?

— Reply to this email directly or view it on GitHub.

By Administrator on 2013-05-14T14:15:19 (imported from GitLab project)

Created by: bbodenmiller

Please check with 5.2.

By Administrator on 2013-06-08T13:29:26 (imported from GitLab project)

Created by: btate

Thanks Ben. I'm in the process of getting more resources allocated to the server gitlab is on. Once I have that I'll upgrade and let you know.

Thanks, Brandon

On Jun 8, 2013, at 9:29 AM, Ben Bodenmiller notifications@github.com wrote:

Please check with 5.2.

— Reply to this email directly or view it on GitHub.

By Administrator on 2013-06-11T17:08:32 (imported from GitLab project)

Created by: jvanbaarsen

@btate Did you manage to fix your issue?

By Administrator on 2013-12-05T11:17:23 (imported from GitLab project)

Created by: jvanbaarsen

@dosire I think this issue can be closed, since its from the 4.2 release

By Administrator on 2013-12-05T12:06:35 (imported from GitLab project)