All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Vlasov <renton@renton.name>
To: linux-kernel@vger.kernel.org
Subject: Kernel migration eat CPUs
Date: Thu, 22 Aug 2013 19:00:46 +0400	[thread overview]
Message-ID: <20130822150046.GF13676@beaver> (raw)

Hi,

Beginning from 3.7 including 3.10 kernel, I noticed that from time to
time all CPUs turn out to be busy 100% and at the moment websites of my
clients work slowly or don’t work at all.

top screen:
https://www.dropbox.com/s/psuk2cwn6exinyd/3.9.cpu_migration.jpg

All CPUs are busy with kernel threads migration for about 3-5 minutes.
Exactly how often it periodically happens I don’t know, but it happens
once in 1-3 hours.

Approximately 30 my servers work on kernel 2.6.35 and there’s no such
problem there. We use kernels 3.7 – 3.9 on 5 servers and I see such
effect everywhere. If you downgrade on 2.6.35, then migration doesn’t
eat CPUs.

These servers are used for usual LAMP shared hosting.

Can I get migration as if on the kernel 2.6.35 or can this feature be
disabled?

-- 
BRGDS. Alexey Vlasov.
jabber: renton@1gb.ru
icq: 5128664

             reply	other threads:[~2013-08-22 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 15:00 Alexey Vlasov [this message]
2013-08-29  7:31 ` Kernel migration eat CPUs Mike Galbraith
     [not found] <20130823151711.f4c1f596b4c7aa1eecccc9a6@linux-foundation.org>
     [not found] ` <20130825142837.GD31370@twins.programming.kicks-ass.net>
2013-08-29 10:10   ` Alexey Vlasov
2013-09-04 18:53   ` Alexey Vlasov
2013-09-05 11:12     ` Ingo Molnar
2013-09-11 15:18       ` Alexey Vlasov
2013-10-10  7:13         ` Alexey Vlasov

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=20130822150046.GF13676@beaver \
    --to=renton@renton.name \
    --cc=linux-kernel@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.