Increase the range of WasmFunctionsPerModule histogram.
Looking at UMA results, we are getting a fair number of modules with more than 10,000 functions (5.2%) that are being lumped into the maximal entry. To get more visibility into what values are being lumped, this CL lifts the maximum to 100,000. BUG=chromium:704922 R=bbudge@chromium.org,bradnelson@chromium.org Review-Url: https://codereview.chromium.org/2787163002 Cr-Commit-Position: refs/heads/master@{#44314}
This commit is contained in:
parent
9fc6398f72
commit
8ed72f91a0
@ -925,10 +925,10 @@ class RuntimeCallTimerScope {
|
||||
HR(scavenge_reason, V8.GCScavengeReason, 0, 21, 22) \
|
||||
HR(young_generation_handling, V8.GCYoungGenerationHandling, 0, 2, 3) \
|
||||
/* Asm/Wasm. */ \
|
||||
HR(wasm_functions_per_asm_module, V8.WasmFunctionsPerModule.asm, 1, 10000, \
|
||||
HR(wasm_functions_per_asm_module, V8.WasmFunctionsPerModule.asm, 1, 100000, \
|
||||
51) \
|
||||
HR(wasm_functions_per_wasm_module, V8.WasmFunctionsPerModule.wasm, 1, 10000, \
|
||||
51)
|
||||
HR(wasm_functions_per_wasm_module, V8.WasmFunctionsPerModule.wasm, 1, \
|
||||
100000, 51)
|
||||
|
||||
#define HISTOGRAM_TIMER_LIST(HT) \
|
||||
/* Garbage collection timers. */ \
|
||||
|
Loading…
Reference in New Issue
Block a user