Add some perf tests to compare Mojo overhead.

Add some perf tests to compare Mojo overhead.

Specifically, this compares making mojo interface calls vs just sending raw IPC::Messages or callbacks.

Review-Url: https://codereview.chromium.org/2608403002
Cr-Commit-Position: refs/heads/master@{#442016}
Committed: https://chromium.googlesource.com/chromium/src/+/ca86c9e8f039783ad8b5f255995cb79b2a7287bf

[jam, 2017-01-04 00:24:27]

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

[commit-bot: I haz the power, 2017-01-04 00:24:57]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-04 01:07:17]

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

[commit-bot: I haz the power, 2017-01-04 01:07:18]

Dry run: Try jobs failed on following builders:
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jam, 2017-01-04 01:13:36]

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

[commit-bot: I haz the power, 2017-01-04 01:13:56]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[jam, 2017-01-04 01:29:23]

Patchset #1 (id:1) has been deleted

[commit-bot: I haz the power, 2017-01-04 02:21:14]

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

[commit-bot: I haz the power, 2017-01-04 02:21:15]

Dry run: This issue passed the CQ dry run.

[jam, 2017-01-05 23:02:29]

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

[commit-bot: I haz the power, 2017-01-05 23:03:01]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-05 23:33:57]

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

[commit-bot: I haz the power, 2017-01-05 23:33:57]

Dry run: Try jobs failed on following builders:
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jam, 2017-01-05 23:40:28]

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

[commit-bot: I haz the power, 2017-01-05 23:40:56]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-06 00:38:46]

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

[commit-bot: I haz the power, 2017-01-06 00:38:47]

Dry run: This issue passed the CQ dry run.

[jam, 2017-01-06 00:56:37]

Patchset #2 (id:40001) has been deleted

[jam, 2017-01-06 00:57:16]

Description was changed from

==========
Add some perf tests to compare Mojo overhead.

BUG=
==========

to

==========
Add some perf tests to compare Mojo overhead.

Specifically, this compares making mojo interface calls vs just sending raw
IPC::Messages or callbacks.
==========

[jam, 2017-01-06 00:57:16]

jam@chromium.org changed reviewers:
+ rockot@chromium.org

[Ken Rockot(use gerrit already), 2017-01-06 18:15:07]

lgtm

https://codereview.chromium.org/2608403002/diff/60001/ipc/run_all_perftests.cc
File ipc/run_all_perftests.cc (right):

https://codereview.chromium.org/2608403002/diff/60001/ipc/run_all_perftests.c...
ipc/run_all_perftests.cc:21: // loop, which is destructed inside
base::LaunchUnitTests.
This is actually not true anymore. ShutdownIPCSupport does useful things,
particularly in multiprocess. It might not affect these tests (unclear), but it
doesn't matter: ScopedIPCSupport can safely be constructed on the stack here and
its destructor will work with or without a MessageLoop.

[jam, 2017-01-06 18:24:18]

https://codereview.chromium.org/2608403002/diff/60001/ipc/run_all_perftests.cc
File ipc/run_all_perftests.cc (right):

https://codereview.chromium.org/2608403002/diff/60001/ipc/run_all_perftests.c...
ipc/run_all_perftests.cc:21: // loop, which is destructed inside
base::LaunchUnitTests.
On 2017/01/06 18:15:07, Ken Rockot wrote:
> This is actually not true anymore. ShutdownIPCSupport does useful things,
> particularly in multiprocess. It might not affect these tests (unclear), but
it
> doesn't matter: ScopedIPCSupport can safely be constructed on the stack here
and
> its destructor will work with or without a MessageLoop.

ah ok, I had copied that from the other run_all_perftests files. I've confirmed
this isn't needed, so updated both.

[jam, 2017-01-06 18:26:23]

The CQ bit was checked by jam@chromium.org

[jam, 2017-01-06 18:26:24]

The patchset sent to the CQ was uploaded after l-g-t-m from rockot@chromium.org
Link to the patchset: https://codereview.chromium.org/2608403002/#ps80001
(title: "review comment")

[commit-bot: I haz the power, 2017-01-06 18:26:57]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-01-06 19:56:01]

CQ is committing da patch.

Bot data: {"patchset_id": 80001, "attempt_start_ts": 1483727183723560,
"parent_rev": "a37268b72ce9073ad0dd298c3576ca1a66832688", "commit_rev":
"ca86c9e8f039783ad8b5f255995cb79b2a7287bf"}

[commit-bot: I haz the power, 2017-01-06 19:56:36]

Description was changed from

==========
Add some perf tests to compare Mojo overhead.

Specifically, this compares making mojo interface calls vs just sending raw
IPC::Messages or callbacks.
==========

to

==========
Add some perf tests to compare Mojo overhead.

Specifically, this compares making mojo interface calls vs just sending raw
IPC::Messages or callbacks.

Review-Url: https://codereview.chromium.org/2608403002
Cr-Commit-Position: refs/heads/master@{#442016}
Committed:
https://chromium.googlesource.com/chromium/src/+/ca86c9e8f039783ad8b5f255995c...
==========

[commit-bot: I haz the power, 2017-01-06 19:56:39]

Committed patchset #3 (id:80001) as
https://chromium.googlesource.com/chromium/src/+/ca86c9e8f039783ad8b5f255995c...