Update sizes to account for http://crrev.com/110076 and others.

Update sizes to account for http://crrev.com/110076 and others.

linux-release/sizes:
http://build.chromium.org/f/chromium/perf/linux-release/sizes/report.html?history=1500&rev=110802&graph=chrome-si

linux-release-64/sizes
http://build.chromium.org/f/chromium/perf/linux-release-64/sizes/report.html?history=1500&rev=110802&graph=chrome-si

TBR=cmp@chromium.org
BUG=none
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=110964

[cmp, 2011-11-21 17:47:55]

lgtm

[cmp, 2011-11-21 17:49:02]

Remember that by including URLs that have 'rev=-1' in them, the URLs will always
show the latest "N results" (where N is specified by history).  You should get
in the habit of using rev=<an actual revision> so the URLs will work in
perpetuity going forward.

[kerz_chromium, 2011-11-21 17:52:40]

On 2011/11/21 17:49:02, cmp wrote:
> Remember that by including URLs that have 'rev=-1' in them, the URLs will
always
> show the latest "N results" (where N is specified by history).  You should get
> in the habit of using rev=<an actual revision> so the URLs will work in
> perpetuity going forward.

Sorry, had changed them in my buffer after, but not here.  Would be nice if the
links from the waterfall were linked in time to the results somehow.

[cmp, 2011-11-21 17:57:57]

On 2011/11/21 17:52:40, kerz_chromium wrote:
> Sorry, had changed them in my buffer after, but not here.

No problem.

> Would be nice if the links from the waterfall were linked in time
> to the results somehow.

I agree, I think it's necessary.  Expect that to happen automatically at some
point.  If you want to get involved with the code, I can show you exactly what
to change and how to test, it should be easy, just needs cycles.