* Juan Quintela (quint...@redhat.com) wrote: > We can scale much better with 16, so we can scale to higher numbers. > > Signed-off-by: Juan Quintela <quint...@redhat.com> > --- > migration/migration.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/migration/migration.c b/migration/migration.c > index 354ad072fa..e7f707e033 100644 > --- a/migration/migration.c > +++ b/migration/migration.c > @@ -86,7 +86,7 @@ > > /* The delay time (in ms) between two COLO checkpoints */ > #define DEFAULT_MIGRATE_X_CHECKPOINT_DELAY (200 * 100) > -#define DEFAULT_MIGRATE_MULTIFD_CHANNELS 2 > +#define DEFAULT_MIGRATE_MULTIFD_CHANNELS 16
OK, I suspect the management apps will set it anyway; some could be a bit surprised chewing 16 cores/threads of CPU in some cases. Reviewed-by: Dr. David Alan Gilbert <dgilb...@redhat.com> > /* Background transfer rate for postcopy, 0 means unlimited, note > * that page requests can still exceed this limit. > -- > 2.23.0 > -- Dr. David Alan Gilbert / dgilb...@redhat.com / Manchester, UK
