MediaRecorderPerf results not consistent to VEAPerf |
|
Issue description1. hw_cpu_usage of reef is 60, while cpu usage from VEAPerf is 30 https://tedlai.users.x20web.corp.google.com/crosbolt_dev/time_series/video_MediaRecorderPerf/hw_cpu_usage.html?sku_filter= https://chromeperf.appspot.com/report?sid=dbafa75f72b88ff2deba8f0ba40757167070859cd9eb373e171b4bee2e95de5b 2. hw_frame_processing_time of some devices are 60, which is too high. https://tedlai.users.x20web.corp.google.com/crosbolt_dev/time_series/video_MediaRecorderPerf/hw_frame_processing_time.html?sku_filter=
,
Feb 13 2018
Additional 30% of cpu usage difference with Chrome running may be reasonable, but the hw_frame_processing_time doesn't sound right. It's it's indeed 60 then it was only encoding at ~15 fps, which is too low if HW encoder is used. |
|
►
Sign in to add a comment |
|
Comment 1 by wuchengli@chromium.org
, Feb 13 2018