Bug 87538 - webkit-patch optimize-baselines should add/delete files in batches from the vcs
Summary: webkit-patch optimize-baselines should add/delete files in batches from the vcs
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Dirk Pranke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-25 15:05 PDT by Dirk Pranke
Modified: 2012-06-08 10:28 PDT (History)
5 users (show)

See Also:


Attachments
Patch (2.66 KB, patch)
2012-05-25 15:05 PDT, Dirk Pranke
ojan: review+
Details | Formatted Diff | Diff
webkit-patch-rebaseline-expectations.txt (38.98 KB, text/plain)
2012-06-07 23:08 PDT, noel gordon
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Pranke 2012-05-25 15:05:01 PDT
webkit-patch optimize-baselines should add/delete files in batches from the vcs
Comment 1 Dirk Pranke 2012-05-25 15:05:42 PDT
Created attachment 144153 [details]
Patch
Comment 2 Ojan Vafai 2012-05-25 15:21:12 PDT
Comment on attachment 144153 [details]
Patch

Wow. That was easy. I suppose this is covered by existing tests? If so, the changelog description should say so.
Comment 3 Ojan Vafai 2012-05-25 15:22:33 PDT
Do we pass all the tests from garden-o-matic to a single "webkit-patch optimize-baselines"?
Comment 4 Dirk Pranke 2012-05-25 15:43:26 PDT
(In reply to comment #2)
> (From update of attachment 144153 [details])
> Wow. That was easy. I suppose this is covered by existing tests? If so, the changelog description should say so.

I will double-check the test coverage and update the change log (and add tests) accordingly.

We optimize one test at a time. 

If we start to rebaseline multiple tests at once using garden-o-matic (or whatever) we will probably want to either extend optimize-baselines to take a list of tests or defer the scm modifications and do it all at once at the end like we're gonna do with rebaseline-test.
Comment 5 Ojan Vafai 2012-05-25 15:50:46 PDT
(In reply to comment #4)
> (In reply to comment #2)
> > (From update of attachment 144153 [details] [details])
> > Wow. That was easy. I suppose this is covered by existing tests? If so, the changelog description should say so.
> 
> I will double-check the test coverage and update the change log (and add tests) accordingly.
> 
> We optimize one test at a time. 
> 
> If we start to rebaseline multiple tests at once using garden-o-matic (or whatever) we will probably want to either extend optimize-baselines to take a list of tests or defer the scm modifications and do it all at once at the end like we're gonna do with rebaseline-test.

Makes sense. I suppose it's rare that garden-o-matic does multiple tests at once. Although, I've had times when I've queued up tons of rebaselines that in theory could be batched. But maybe with all these performance improvements it won't matter.
Comment 6 Adam Barth 2012-05-25 16:15:35 PDT
Comment on attachment 144153 [details]
Patch

It's important to do all the deletes before the adds, which you've done.  Thanks.
Comment 7 Dirk Pranke 2012-05-25 16:38:29 PDT
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #2)
> > > (From update of attachment 144153 [details] [details] [details])
> > > Wow. That was easy. I suppose this is covered by existing tests? If so, the changelog description should say so.
> > 
> > I will double-check the test coverage and update the change log (and add tests) accordingly.
> > 
> > We optimize one test at a time. 
> > 
> > If we start to rebaseline multiple tests at once using garden-o-matic (or whatever) we will probably want to either extend optimize-baselines to take a list of tests or defer the scm modifications and do it all at once at the end like we're gonna do with rebaseline-test.
> 
> Makes sense. I suppose it's rare that garden-o-matic does multiple tests at once. Although, I've had times when I've queued up tons of rebaselines that in theory could be batched. But maybe with all these performance improvements it won't matter.

I think there still could be wins from pipelining multiple tests through and batching more things. Since the 'rebaselineall' http entry point does take multiple lists, it won't be hard to extend the backend if we need it to. Even with all of these improvements, Rebaselining still is multiple seconds per test over a fast network. We should have somebody test this from asia or europe to see how it is from there.
Comment 8 Ojan Vafai 2012-05-25 16:43:41 PDT
I nominate Noel once this and https://bugs.webkit.org/show_bug.cgi?id=87451 are committed.
Comment 9 noel gordon 2012-05-25 20:05:23 PDT
Happy to do it.  Let me know what you need when you're ready.
Comment 10 Dirk Pranke 2012-05-29 14:46:39 PDT
Committed r118838: <http://trac.webkit.org/changeset/118838>
Comment 11 noel gordon 2012-06-07 23:08:21 PDT
Created attachment 146485 [details]
webkit-patch-rebaseline-expectations.txt

Timing: rebaseline one test from AEST time zone.
Comment 12 Ojan Vafai 2012-06-08 09:36:45 PDT
(In reply to comment #11)
> Created an attachment (id=146485) [details]
> webkit-patch-rebaseline-expectations.txt
> 
> Timing: rebaseline one test from AEST time zone.

Unfortunately, webkit-patch rebaseline-expectations doesn't yet do the rebaselines in parallel. We only do them in parallel from garden-o-matic. So, this 21 seconds is the time to do it serially. Looking at the output here, doing the rebaselines in parallel should cut the time down to ~5 seconds.
Comment 13 noel gordon 2012-06-08 10:28:36 PDT
5 seconds sounds good.  "Let me know what you need when you're ready." ... and so with no news, I just punted that webkit-patch rebaseline-expectations had the new fancy :)