[openstack-qa] Priolity brainstorming my initial toughts

Giulio Fidente gfidente at redhat.com
Mon Jun 17 08:06:04 UTC 2013

On 06/17/2013 12:42 AM, Daryl Walleck wrote:
> Here's the benchmarks I came up with based on comparing test_server_actions with the exact same tests broken down into individual classes (see https://github.com/stackforge/cloudroast/tree/master/test_repo/compute/functional/servers/actions).
> Devstack
> -------------------------------------------
> Current Tempest: 262.030s
> Discussed Alternative (broken down into test classes and run in parallel): 98.342s

Daryl, that's ~3 times faster but are you parallelizing the execution of 
the classes or of the test cases (duplicating the setUpClass steps)?

In his email Matthew suggests that, given our current usage of 
setUpClass, parallelizing every single test case won't produce better 

To leverage the classes parallelization instead, after the changes in 
testr will be available, maybe we could just revisit the tests and try 
to split them across more classes to allow for better partitioning.
Giulio Fidente
GPG KEY: 08D733BA | IRC: giulivo

More information about the openstack-qa mailing list