Commit 668a8427 authored by Jakob Gruber's avatar Jakob Gruber Committed by V8 LUCI CQ

Remove the runtime_profiler_ticks counter

Now that different tiers use dedicated interrupt_budgets (which
determine how often the runtime profiler (now tiering manager) is
called), I don't see a meaningful way to use results from this counter.

Bug: v8:7700
Change-Id: I2ec2242d3c7f6c2b9deab075a6f0500cc1350e96
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3467595Reviewed-by: 's avatarCamillo Bruni <cbruni@chromium.org>
Commit-Queue: Jakob Gruber <jgruber@chromium.org>
Cr-Commit-Position: refs/heads/main@{#79117}
parent 3f03910c
......@@ -246,8 +246,6 @@ TieringManager::OnInterruptTickScope::~OnInterruptTickScope() {
}
void TieringManager::OnInterruptTick(JavaScriptFrame* frame) {
isolate_->counters()->runtime_profiler_ticks()->Increment();
if (!isolate_->use_optimizer()) return;
OnInterruptTickScope scope(this);
......
......@@ -340,7 +340,6 @@ namespace internal {
SC(sub_string_runtime, V8.SubStringRuntime) \
SC(regexp_entry_runtime, V8.RegExpEntryRuntime) \
SC(stack_interrupts, V8.StackInterrupts) \
SC(runtime_profiler_ticks, V8.RuntimeProfilerTicks) \
SC(soft_deopts_executed, V8.SoftDeoptsExecuted) \
SC(new_space_bytes_available, V8.MemoryNewSpaceBytesAvailable) \
SC(new_space_bytes_committed, V8.MemoryNewSpaceBytesCommitted) \
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment