Comment #3 on issue 9603 by [email protected]: run_webkit_tests should be faster http://code.google.com/p/chromium/issues/detail?id=9603
I did some quick profiling of run_webkit_tests.py on my mac quad-core using 4 test_shells at once and >99% of the time was spent in thread.wait (i.e. waiting for test_shell). ~3-4 seconds was spent in actual python processing. So, I'm pretty convinced that the only way to improve performance is the above sharding work and reducing the timeout in the process of fixing issue 9324 and/or improving the performance of test_shell itself. I didn't profile on Windows or Linux or with fewer/greater cores, but it doesn't seem worth the effort. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
