mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org, Bob Copeland <me@bobcopeland.com>
Subject: Re: git pull on linux-next makes my system crawl to its knees and beg  for mercy
Date: Wed, 23 Dec 2009 18:11:36 +0100	[thread overview]
Message-ID: <1158166a0912230911o5c33adfcg9a39da22aec7b44a@mail.gmail.com> (raw)
In-Reply-To: <43e72e890912230820j5e00b8cbq9ea9009cdcf25a0f@mail.gmail.com>

On Wed, Dec 23, 2009 at 5:20 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>> Is it allocating/using so much memory
>> that your box goes into a severe swap storm?
>
> Could be, 979M virtual, 298M resident size (non swapped), 58665 shared.
>
> Unfortunately when this happens I cannot log into my box and run good
> diagnostics, that's how much of a pain in the bolas this is.

Nicing it may make it easier to do diagnostic work.

> Some
> morning I had enough patience I did leave vmstat and iostat running
> and didn't see much out of the ordinary except CPU wait time was
> pretty high. I did manage to get at least htop running once and took a
> screenshot (and this took me about 10 minutes to generate):
>
> http://bombadil.infradead.org/~mcgrof/images/2009/12/git-merge.jpg

Looks like swap space is 2/3 used. This is an indication
of memory starvation.

It may be a residual condition - you have a lot of potentially
bloated programs running. What do you see if you reproduce
this situation soon after boot, with minimum of other running programs?
For one, definitely do not start web browser(s) and such.
Ideally, do not run X at all.

If you still see a lot of swap used, then this is it - git
requires more memory for this task. The possibility that
kernel has a bug where it needlessly swaps out is remote.

--
vda

      reply	other threads:[~2009-12-23 17:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 17:26 Luis R. Rodriguez
2009-12-18 17:38 ` Bartlomiej Zolnierkiewicz
2009-12-18 19:19   ` Luis R. Rodriguez
2009-12-18 19:55     ` Luis R. Rodriguez
2009-12-18 20:51       ` Luis R. Rodriguez
2009-12-18 21:13         ` Luis R. Rodriguez
2009-12-18 21:56 ` Stephen Rothwell
2009-12-18 22:03   ` Luis R. Rodriguez
2009-12-23 15:27     ` Denys Vlasenko
2009-12-23 16:20       ` Luis R. Rodriguez
2009-12-23 17:11         ` Denys Vlasenko [this message]

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=1158166a0912230911o5c33adfcg9a39da22aec7b44a@mail.gmail.com \
    --to=vda.linux@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=me@bobcopeland.com \
    --cc=sfr@canb.auug.org.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®