Browse files

benchmark: cleanup after forced optimization drop

This removes all instances of %OptimizeFunctionOnNextCall from common.js

PR-URL: #9615
Reviewed-By: James M Snell <>
Reviewed-By: Matteo Collina <>
  • Loading branch information...
bzoz committed Mar 1, 2017
1 parent ca86aa5 commit 75cdc895ec8fd38b3a22535d9f90792c7c7be964
Showing with 0 additions and 23 deletions.
  1. +0 −9 benchmark/
  2. +0 −14 benchmark/common.js
@@ -235,12 +235,3 @@ it returns to accomplish what they need. This function reports timing
data to the parent process (usually created by running `compare.js`, `run.js` or
### v8ForceOptimization(method[, ...args])
Force V8 to mark the `method` for optimization with the native function
`%OptimizeFunctionOnNextCall()` and return the optimization status
after that.
It can be used to prevent the benchmark from getting disrupted by the optimizer
kicking in halfway through. However, this could result in a less effective
optimization. In general, only use it if you know what it actually does.
@@ -229,17 +229,3 @@ = function(rate, elapsed) {
type: 'report'
exports.v8ForceOptimization = function(method) {
if (typeof method !== 'function')
const v8 = require('v8');
const args =, 1);
method.apply(null, args);
method.apply(null, args);
return eval('%GetOptimizationStatus(method)');

0 comments on commit 75cdc89

Please sign in to comment.