Thanks to Ojan for this, the release testers are considerably faster now. As for debug, while we wait for this change to take effect there too, I added some more hardware. Windows, Mac and Linux are now running the webkit dbg layout tests in parallel on 3 machines each.
Nicolas On Mon, Apr 6, 2009 at 6:24 PM, Ojan Vafai <[email protected]> wrote: > run_webkit_test.sh now runs cpus+1 test_shells for Release builds. Please > keep an eye out over the next couple days for test flakyness that may have > resulted from this. > Release tests on a dual core now take about half the time they used to. > There's still a lot of room for improvement and I'm a bit burnt out on this > stuff, so if anyone is willing to help that would be much appreciated. Here > are the remaining obvious things we could do to make a significant > performance improvement: > > 1. Test and turn on parallelizing for Debug builds > 2. Get 4 or 8 core webkit buildbots > 3. Shard LayoutTests/fast and LayoutTests/http. Right now, in order to > reduce test flakiness, we bucket tests by directory and run all those tests > in the same process (thanks to dlevin for this idea!). The problem is that > we're left with two very large buckets that can be further broken down. The > work of breaking them down further is trivial (just add the directory names > to a list in run_webkit_tests.py), the bigger problem is that some flakiness > starts to appear in the fast/http tests when we break them down further. So, > we need people to figure out what the source of the flakiness is and deal > with it appropriately. > > If we did all of the above, I expect we would see at least another factor > of two performance improvement. > > Let me know if you want to help out with any of this. > > Ojan > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
