From: Marek Olšák <marek.ol...@amd.com> This makes piglit 16% faster, because 1 thread per core uses only 85% of the CPU. I don't know why the CPU is idle at times, but I guess it's due to waiting for fences. --- framework/profile.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/framework/profile.py b/framework/profile.py index 94efd0a..61eabd0 100644 --- a/framework/profile.py +++ b/framework/profile.py @@ -423,21 +423,21 @@ def run(profiles, logger, backend, concurrency): # pool run_threads(single, profile, test_list, lambda x: not x[1].run_concurrent) profile.teardown() # Multiprocessing.dummy is a wrapper around Threading that provides a # multiprocessing compatible API # # The default value of pool is the number of virtual processor cores single = multiprocessing.dummy.Pool(1) - multi = multiprocessing.dummy.Pool() + multi = multiprocessing.dummy.Pool(multiprocessing.cpu_count() * 2) try: for p in profiles: run_profile(*p) for pool in [single, multi]: pool.close() pool.join() finally: log.get().summary() -- 2.7.4 _______________________________________________ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit