New issue
Advanced search Search tips

Issue 908699 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

crosvm performance testing

Project Member Reported by za...@chromium.org, Nov 27

Issue description

There are 2 areas of performance testing that should be focused on:

1) Hypervisor time: cycles spent outside of KVM_RUN, but in a cpu thread. 
2) Device time: cycles spent in device threads.

Breaking out user vs kernel vs IO cycles and cpu time would also be handy.

Additionally, Chrome OS has a tracing UI via chrome://tracing. Supporting that would be handy for quick profiling.
 
Status: Assigned (was: Untriaged)
<triage>Marked assigned</triage>

Sign in to add a comment