All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, lvivier@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8 3/8] tests: Add migration xbzrle test
Date: Tue, 8 May 2018 16:38:40 +0100	[thread overview]
Message-ID: <20180508153838.GQ2500@work-vm> (raw)
In-Reply-To: <87sh726uvd.fsf@secure.laptop>

* Juan Quintela (quintela@redhat.com) wrote:
> "Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> > * Juan Quintela (quintela@redhat.com) wrote:
> >> Signed-off-by: Juan Quintela <quintela@redhat.com>
> >> Reviewed-by: Peter Xu <peterx@redhat.com>
> 
> >> +
> >> +    migrate_set_parameter(from, "xbzrle-cache-size", "33554432");
> >
> > I still worry about the cache size relative to the size of memory we're
> > actually changing in the test; I don't quite understand why it's turning
> > out to get lots of hits.
> 
> I planned this as a smorke test.  But what value do you have in mind?

Given the test code dirties 100MB of RAM, I suggest a cache of 110MB
say.  But it's interesting that the stats show we are getting a lot of
page hits; I'm not sure I understand why.

> > Also, xbzrle eats so much CPU we'll still have to watch out for the low
> > end CPUs.
> 
> Any concrete suggestion?
> 
> My plan would have been to push on my next pull request:
> 
> Add migration precopy test
> Add migration xbzrle test
> Migration ppc now inlines its program
> 
> And put the rest of the patches with fixes for another review.

Go with it and lets see; if we hit problems then we can just turn that
300ms downtime limit right up.

Dave

> 
> Later, Juan.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2018-05-08 15:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-25 11:19 [Qemu-devel] [PATCH v8 0/8] Add make check tests for Migration Juan Quintela
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 1/8] qemu-sockets: Export SocketAddress_to_str Juan Quintela
2018-05-02 16:13   ` Dr. David Alan Gilbert
2018-05-02 16:17   ` Daniel P. Berrangé
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 2/8] tests: Add migration precopy test Juan Quintela
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 3/8] tests: Add migration xbzrle test Juan Quintela
2018-05-03 17:31   ` Dr. David Alan Gilbert
2018-05-08 15:16     ` Juan Quintela
2018-05-08 15:38       ` Dr. David Alan Gilbert [this message]
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 4/8] migration: Create socket-address parameter Juan Quintela
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 5/8] tests: Migration ppc now inlines its program Juan Quintela
2018-05-02 11:51   ` Laurent Vivier
2018-05-02 13:41   ` Thomas Huth
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 6/8] tests: Add basic migration precopy tcp test Juan Quintela
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 7/8] migration: Add multifd test Juan Quintela
2018-04-25 11:19 ` [Qemu-devel] [PATCH v8 8/8] [RFH] tests: Add migration compress threads tests Juan Quintela

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=20180508153838.GQ2500@work-vm \
    --to=dgilbert@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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.