New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 827752 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: 2019-07-09
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

memory-eater incorrectly calculating throughput when using swap file

Project Member Reported by asavery@chromium.org, Mar 31 2018

Issue description

memory-eater doesn't seem to be properly measuring time when run on a device using a swap file. When using a swap file, the emmc is fully utilized and it is spending a lot of time waiting for io operations, but this doesn't seem to be factored into the time.

What steps will reproduce the problem?
(1) run the hardware_MemoryZRAMThroughput autotest or run memory-eater on a device using a swap file

What is the expected result?
The page access throughput (using 30% swap if running the autotest)

What happens instead?
The output numbers don't make sense given how long the test is taking to run and the expected performance of the device.



 
Labels: Pri-3
NextAction: 2019-07-09
Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.

Comment 2 by osh...@chromium.org, Jan 18 (4 days ago)

Components: Infra>ChromeOS>Test

Sign in to add a comment