Reland Track memory consumption of SP on top 7 sites.

Track memory consumption of SP on top 7 sites.

Tests:
android: https://codereview.chromium.org/1023783006/
linux & mac: https://codereview.chromium.org/1013723006/
win: https://codereview.chromium.org/1038773002/

All above pass the "Running With Patch" step.

BUG=None

Committed: https://crrev.com/82b8e167143a5f0d4dd4515c6d0e14a64f654083
Cr-Commit-Position: refs/heads/master@{#323680}

[Pan, 2015-04-02 01:02:43]

pan.deng@intel.com changed reviewers:
+ pdr@chromium.org, sullivan@chromium.org

[Pan, 2015-04-03 00:48:37]

can we reland it now? thanks, Pan

[pdr., 2015-04-03 01:15:50]

On 2015/04/03 at 00:48:37, pan.deng wrote:
> can we reland it now? thanks, Pan

Thanks for putting this together. LGTM

[pdr., 2015-04-03 01:15:52]

The CQ bit was checked by pdr@chromium.org

[sullivan, 2015-04-03 01:27:11]

lgtm

[commit-bot: I haz the power, 2015-04-03 04:43:43]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1052843002/1

[commit-bot: I haz the power, 2015-04-03 07:57:30]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-03 20:34:57]

Patchset 1 (id:??) landed as
https://crrev.com/82b8e167143a5f0d4dd4515c6d0e14a64f654083
Cr-Commit-Position: refs/heads/master@{#323680}

[shatch, 2015-04-07 18:32:11]

On 2015/04/03 20:34:57, I haz the power (commit-bot) wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/82b8e167143a5f0d4dd4515c6d0e14a64f654083
> Cr-Commit-Position: refs/heads/master@{#323680}

Did you mean to commit the changes to memory.py and not to run-perf-test.cfg?
This CL seems to only consist of changes to run-perf-test.cfg.

[qyearsley, 2015-04-07 18:45:36]

qyearsley@chromium.org changed reviewers:
+ prasadv@chromium.org

[qyearsley, 2015-04-07 18:47:43]

On 2015/04/07 18:32:11, shatch wrote:
> On 2015/04/03 20:34:57, I haz the power (commit-bot) wrote:
> > Patchset 1 (id:??) landed as
> > https://crrev.com/82b8e167143a5f0d4dd4515c6d0e14a64f654083
> > Cr-Commit-Position: refs/heads/master@{#323680}
> 
> Did you mean to commit the changes to memory.py and not to run-perf-test.cfg?
> This CL seems to only consist of changes to run-perf-test.cfg.

I think that changes to run-perf-test.cfg should generally not be submitted, so
I think this CL should be reverted (and maybe a separate CL should be made to
make the intended changes to memory.py?)

Pan, does that sound right?

[shatch, 2015-04-07 19:11:45]

On 2015/04/07 18:47:43, qyearsley wrote:
> On 2015/04/07 18:32:11, shatch wrote:
> > On 2015/04/03 20:34:57, I haz the power (commit-bot) wrote:
> > > Patchset 1 (id:??) landed as
> > > https://crrev.com/82b8e167143a5f0d4dd4515c6d0e14a64f654083
> > > Cr-Commit-Position: refs/heads/master@{#323680}
> > 
> > Did you mean to commit the changes to memory.py and not to
run-perf-test.cfg?
> > This CL seems to only consist of changes to run-perf-test.cfg.
> 
> I think that changes to run-perf-test.cfg should generally not be submitted,
so
> I think this CL should be reverted (and maybe a separate CL should be made to
> make the intended changes to memory.py?)
> 
> Pan, does that sound right?

I'll just revert this since there are no other files involved except the cfg
file, which shouldn't be submitted.

[shatch, 2015-04-07 19:13:20]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1062253002/ by simonhatch@chromium.org.

The reason for reverting is: I think the original CL meant to make changes to
memory.py, not run-perf-test.cfg. We shouldn't be submitting changes to
run-perf-test.cfg, this file is used by the perf-try bots to pass try job
parameters..

[pdr., 2015-04-07 22:09:51]

On 2015/04/07 at 19:13:20, simonhatch wrote:
> A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1062253002/ by simonhatch@chromium.org.
> 
> The reason for reverting is: I think the original CL meant to make changes to
memory.py, not run-perf-test.cfg. We shouldn't be submitting changes to
run-perf-test.cfg, this file is used by the perf-try bots to pass try job
parameters..

I'm relanding this in https://codereview.chromium.org/1066223002.

[Pan, 2015-04-08 00:37:20]

> > The reason for reverting is: I think the original CL meant to make changes
to
> memory.py, not run-perf-test.cfg. We shouldn't be submitting changes to
> run-perf-test.cfg, this file is used by the perf-try bots to pass try job
> parameters..
> 
> I'm relanding this in https://codereview.chromium.org/1066223002.

Oh, my mistake, thanks, Pan.