New issue
Advanced search Search tips

Issue 759845 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 715175



Sign in to add a comment

Investigate CPU usage of the Mojo and legacy IPC system

Project Member Reported by yzshen@chromium.org, Aug 28 2017

Issue description

.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4d50dc4ccb461f6daf8572b67f2216acec704d1c

commit 4d50dc4ccb461f6daf8572b67f2216acec704d1c
Author: Yuzhu Shen <yzshen@chromium.org>
Date: Wed Sep 06 20:39:09 2017

Add CPU usage perf tests for legacy IPC and Mojo.

These tests do async/sync ping-pongs between two processes for legacy IPC/Mojo.
They do it in a somewhat fixed-rate manner: split one second into a fixed
amount of "frames", and do a fixed amount of ping-pongs for each frame.

Current numbers:
Linux; release component build; Z620
Test name description:
 * Async / Sync: Whether ping-pong is done using async messages or sync messages.
 * MsgSize: Size of each message, in bytes.
 * FrmPerSec: Frames per second.
 * MsgPerFrm: How many messages sent and received (i.e., round trips) per frame.

Test result: The percentage of a CPU core used during the test, on average.
(It could be the sum of cost on multiple cores.)

[ RUN      ] ChannelSteadyPingPongTest.AsyncPingPong
IPC_CPU_Async_MsgSize_144_FrmPerSec_20_MsgPerFrm_10	5.68031	%
IPC_CPU_Async_MsgSize_144_FrmPerSec_60_MsgPerFrm_10	15.7017	%

[ RUN      ] ChannelSteadyPingPongTest.SyncPingPong
IPC_CPU_Sync_MsgSize_144_FrmPerSec_20_MsgPerFrm_10	5.68387	%
IPC_CPU_Sync_MsgSize_144_FrmPerSec_60_MsgPerFrm_10	15.4848	%

[ RUN      ] MojoSteadyPingPongTest.AsyncPingPong
Mojo_CPU_Async_MsgSize_144_FrmPerSec_20_MsgPerFrm_10	3.68818	%
Mojo_CPU_Async_MsgSize_144_FrmPerSec_60_MsgPerFrm_10	10.2393	%

[ RUN      ] MojoSteadyPingPongTest.SyncPingPong
Mojo_CPU_Sync_MsgSize_144_FrmPerSec_20_MsgPerFrm_10	3.69054	%
Mojo_CPU_Sync_MsgSize_144_FrmPerSec_60_MsgPerFrm_10	10.7317	%


Bug: 759845
Change-Id: Idc8139a90c3175193aab68a8fc91d1aeac1aa340
Reviewed-on: https://chromium-review.googlesource.com/639340
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Yuzhu Shen <yzshen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#500074}
[modify] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/BUILD.gn
[modify] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/DEPS
[modify] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/OWNERS
[add] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/ipc_cpu_perftest.cc
[modify] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/ipc_mojo_perftest.cc
[add] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/ipc_perftest_messages.cc
[add] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/ipc_perftest_messages.h
[add] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/ipc_perftest_util.cc
[add] https://crrev.com/4d50dc4ccb461f6daf8572b67f2216acec704d1c/ipc/ipc_perftest_util.h

Comment 2 by yzshen@chromium.org, Feb 15 2018

Owner: ----
Status: Available (was: Assigned)

Sign in to add a comment