Pontential jankiness caused by deserializing many call stack profiles at one time |
|||
Issue descriptionOS: Win, MacOS We serialize all the call stack profiles in memory because this is memory efficient. We need to deserialize them when uploading them to UMA servers. Local test in my beefy corp machine shows deserializing a profile takes about 1 ms. In the extreme case where there are 1250 (due to a cap) profiles pending upload, serializing all of them in a row takes 1+ second. Since this is happening on UI thread, the jankiness can be a problem.
,
Nov 22
,
Nov 22
,
Nov 27
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9606c6d7592331575a7ff1130d6069c764d30c0e commit 9606c6d7592331575a7ff1130d6069c764d30c0e Author: Xi Cheng <chengx@chromium.org> Date: Tue Nov 27 17:59:19 2018 Record the time cost of deserializing all pending call stack profiles Bug: 903972 Change-Id: Ib70702de4cda80970454fd5d8c296855673698cb Reviewed-on: https://chromium-review.googlesource.com/c/1347145 Reviewed-by: Mike Wittman <wittman@chromium.org> Reviewed-by: Ilya Sherman <isherman@chromium.org> Commit-Queue: Xi Cheng <chengx@chromium.org> Cr-Commit-Position: refs/heads/master@{#611182} [modify] https://crrev.com/9606c6d7592331575a7ff1130d6069c764d30c0e/components/metrics/call_stack_profile_metrics_provider.cc [modify] https://crrev.com/9606c6d7592331575a7ff1130d6069c764d30c0e/tools/metrics/histograms/histograms.xml |
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Nov 20