All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kanis <expire-by-2010-08-09@kanis.fr>
To: git@vger.kernel.org
Subject: Git server eats all memory
Date: Wed, 04 Aug 2010 16:57:39 +0200	[thread overview]
Message-ID: <wesfwyupgrg.fsf@kanis.fr> (raw)

Hello,

I am running git 1.7.0.4 on Debian stable. I have compiled git from
source. I am cloning using ssh.The client and the server are running
the same version. The bare repository is 4.5G with various binary files,
I have 6G of memory on my server.

I am having problem with memory ballooning when receiving object
from the server. The amount of memory used on the server seems to be same
size as the object received.

I have been discussing this quite a bit on #git at freenode. Hilary said
it was maybe due to file mmap that caused the memory reported on top to
be skewed.

I have ran two clones side by side and noticed that the server started
to swap and performance were awful. This means that if two developers
are doing a clone at the same time they will notice the slowness. 

Another worry is that we're planning to have more repositories of the
same size and the server just won't scale.

I am wondering if anyone has seen this behavior? I'll do whatever I can
to troubleshoot the problem. I know C but I just don't know where to
look at. Any help would be very much appreciated.

Kind regards,
-- 
Ivan Kanis

Let a fool hold his tongue and he will pass for a sage.
    -- Publilius Syrus 

             reply	other threads:[~2010-08-04 15:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 14:57 Ivan Kanis [this message]
2010-08-04 15:55 ` Git server eats all memory Matthieu Moy
2010-08-04 17:50   ` Ivan Kanis
2010-08-04 20:12 ` Avery Pennarun
2010-08-05  6:33   ` Ivan Kanis
2010-08-05 22:45     ` Jared Hance
2010-08-06  1:37     ` Nguyen Thai Ngoc Duy
2010-08-06  1:51       ` Nguyen Thai Ngoc Duy
2010-08-06 11:34         ` Jakub Narebski
2010-08-06 17:23         ` Ivan Kanis
2010-08-07  6:42           ` Dmitry Potapov
2010-08-09 10:12             ` Excessive mmap [was Git server eats all memory] Ivan Kanis
2010-08-09 12:35               ` Dmitry Potapov
2010-08-09 16:34                 ` Ivan Kanis
2010-08-09 16:50                   ` Avery Pennarun
2010-08-09 17:45                     ` Tomas Carnecky
2010-08-09 18:17                       ` Avery Pennarun
2010-08-09 21:28                     ` Dmitry Potapov
2010-08-11 15:47                     ` Ivan Kanis
2010-08-11 16:35                       ` Avery Pennarun
     [not found]                         ` <wes4oetv31i.fsf@kanis.fr>
2010-08-17 17:07                           ` Dmitry Potapov
2018-06-20 14:53               ` Duy Nguyen
     [not found]           ` <AANLkTi=yeTh2tKn9t_=iZbdB5VLrfCPZ2_fBpYdf9wta@mail.gmail.com>
     [not found]             ` <wesbp9cnnag.fsf@kanis.fr>
2010-08-09  9:57               ` Git server eats all memory Nguyen Thai Ngoc Duy
2010-08-09 17:38                 ` Ivan Kanis
2010-08-10  0:46 ` Robin H. Johnson
2010-08-10  2:31   ` Sverre Rabbelier
2010-08-11 10:30     ` Sam Vilain
2010-08-11 15:54   ` Ivan Kanis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wesfwyupgrg.fsf@kanis.fr \
    --to=expire-by-2010-08-09@kanis.fr \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.