From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC] KVM-Autotest: basic parallel test execution Date: Sun, 24 May 2009 17:46:28 +0300 Message-ID: <4A195DC4.806@redhat.com> References: <360943614.47181242571294363.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <1294159996.47211242571742642.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> <20090520205210.GU6905@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Michael Goldish , KVM List To: Ryan Harper Return-path: Received: from mx2.redhat.com ([66.187.237.31]:46254 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751423AbZEXOqa (ORCPT ); Sun, 24 May 2009 10:46:30 -0400 In-Reply-To: <20090520205210.GU6905@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Ryan Harper wrote: > I took a slightly different approach. The kvm_tests.cfg file already > provides a dependency relationship between different tests. I modified > the main loop in the control file to walk the entire list of jobs and > pull out any jobs that don't have any dependencies (ie, install tests). > And then run N jobs in parallel from that list until it is exhausted; > then store the results. Then loop the over the remaining list of jobs > again finding the jobs that can be run. > > On a larger multi core system, one might set the number of parallel jobs > equal to the number of cores. > > I think this works well with using autoserv to farm out different > kvm_tests.cfg to different machines. > This is my preference as well, though I think scheduling needs to be cleverer. Each test should specify how much memory and how many cores (the -m and -smp parameters) it needs, and the scheduler needs to make sure we don't over commit the host for tests. This ensures the best utilization while not interfering with test timing. -- error compiling committee.c: too many arguments to function