[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] reliable live migration of large and busy guests
On Wed, Nov 7, 2012 at 3:10 PM, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> wrote: > From an idealistic point of view, it might be quite nice to have several Was he against a hybrid approach, where you "push" things first, and then "pull" things later? Or just against a pure "pull" approach? I'm pretty sure a pure "pull" approach would result in lower performance during the migration. Just tossing another idea out there: What about throttling the VM if it's dirtying too many pages? You can use the "cap" feature of the credit1 scheduler to reduce the amount of cpu time a given VM gets, even if there is free cpu time available. You could play around with doing N iterations, and then cranking down the cap on each iteration after that; then the application wouldn't have a several-second pause, it would just be "running slowly" for some period of time. Overall doing a hybrid "send dirty pages for a while, then move and pull the rest in" seems like the best approach in the long-run, but it's fairly complicated. A throttling approach is probably less optimal but simpler to get working as a temporary measure. -George _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |