All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Byrne <john.l.byrne@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Live migration: "netbuf race" messages can cause significant perfomance impact
Date: Wed, 20 Dec 2006 19:00:16 -0800	[thread overview]
Message-ID: <4589F8C0.30809@hp.com> (raw)


Hi,

Someone found that doing a live migration of a domain that had ballooned 
down took far longer to migrate. (Ballooned down from 3000M to 1000M, 31 
seconds vs 89 seconds, real time) I came up with a complex theory and 
asked him to look in the xend.log to confirm it. He didn't, but he 
mentioned there was a lot of "netbuf race" messages in the log. In this 
particular case, live migration generated approximately 512000 "netbuf 
race" messages. Deleting the DPRINTF reduced the migration time to 11 
seconds.

While it is simple enough to submit a patch to delete this DPRINTF, 
perhaps something more subtle is called for such as modifying the 
migrate/save command paths to accept a debug argument and passing to 
xc_save?

Thanks,

John Byrne

             reply	other threads:[~2006-12-21  3:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  3:00 John Byrne [this message]
2006-12-21 18:18 ` Live migration: "netbuf race" messages can cause significant perfomance impact Ian Pratt
2006-12-29 13:07 ` Steven Hand

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=4589F8C0.30809@hp.com \
    --to=john.l.byrne@hp.com \
    --cc=xen-devel@lists.xensource.com \
    /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.