• Camillo Bruni's avatar
    Revert "[DevTools] Implemented DevTools protocol API to retrieve V8 RunTime Call Stats." · a016cce5
    Camillo Bruni authored
    This reverts commit 91c8be95.
    
    RCS should not be exposed through the API or the inspector protocol as
    they are meant as an internal debugging feature.
    The only regularly tested and supported way is through chrome-tracing.
    
    Given that this was used mostly for an experiment to analyse chrome's
    performance, we can use pprof support as a replacement.
    
    Original change's description:
    > [DevTools] Implemented DevTools protocol API to retrieve V8 RunTime Call Stats.
    >
    > The new APIs are:
    > enableRuntimeCallStats
    > disableRuntimeCallStats
    > getRuntimeCallStats
    >
    > The RunTime Call Stats are collected per isolate.
    >
    > Change-Id: I7e520e2c866288aa9f9dc74f12572abedf0d3ac8
    > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1881601
    > Commit-Queue: Peter Kvitek <kvitekp@chromium.org>
    > Reviewed-by: Yang Guo <yangguo@chromium.org>
    > Cr-Commit-Position: refs/heads/master@{#64784}
    
    Change-Id: Ia7575436e97d3420dd7e68414d89477e6a86bb05
    Bug: v8:11395
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2998585Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
    Commit-Queue: Camillo Bruni <cbruni@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#76297}
    a016cce5
runtime-call-stats.cc 11.4 KB