Fix regression in memory-infra bots due to change in dump order

Fix regression in memory-infra bots due to change in dump order

crrev.com/1427963002 introduced a new memory-infra thread which runs
after all dump providers are finished. This measures the process total
memory usages. This was previously running at the start of a memory
dump. This means that the memory used while taking memory dump of other
providers will be included in the totals now and this metric has
regressed. This CL is a temporary change that reverts this behaviour so
that the perf bots are happy. Better fix for the problem will follow up
soon.

BUG=555584
Committed: https://crrev.com/ef89c2a502dadf4458000278ef4befbd79523bf8
Cr-Commit-Position: refs/heads/master@{#361126}

[ssid, 2015-11-23 12:22:23]

ssid@chromium.org changed reviewers:
+ dsinclair@chromium.org, picksi@chromium.org, primiano@chromium.org

[ssid, 2015-11-23 12:22:23]

+dsinclair PTAL at this change. This is temporary fix for the regression since
primiano is OOO and once he returns he will get a better fix in.

+primiano FYI.

[Primiano Tucci (use gerrit), 2015-11-23 15:25:39]

LGTM if this is really needed.
+CC TOK, I guess this will influence their benchmark as well.
P.S. You might want to add a short URL to the chromeperf dashboard that shows
the regression.

[ssid, 2015-11-23 16:27:17]

On 2015/11/23 15:25:39, Primiano Tucci wrote:
> LGTM if this is really needed.
> +CC TOK, I guess this will influence their benchmark as well.
> P.S. You might want to add a short URL to the chromeperf dashboard that shows
> the regression.

Hm, the graph is already in the bug, so not adding it.

[ssid, 2015-11-23 16:27:24]

The CQ bit was checked by ssid@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-11-23 16:28:07]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1466293002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1466293002/1

[commit-bot: I haz the power, 2015-11-23 17:04:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-11-23 17:04:23]

Dry run: This issue passed the CQ dry run.

[ssid, 2015-11-23 17:07:14]

The CQ bit was checked by ssid@chromium.org

[commit-bot: I haz the power, 2015-11-23 17:07:41]

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

[commit-bot: I haz the power, 2015-11-23 17:14:00]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-23 17:15:03]

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

[haraken, 2015-11-24 01:00:15]

LGTM

[ssid, 2015-11-26 13:45:41]

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

The reason for reverting is: Along with this CL, the memory-infra build was
broken (fixed in https://codereview.chromium.org/1474543003/). But, this cause
much noise in the metrics and did not give a clear idea if the change fixed the
original regression. So, I will revert this again and re-land it to check if
that actually makes a difference..