benchmark: cleanup after forced optimization drop
This removes all instances of %OptimizeFunctionOnNextCall from common.js and README.md PR-URL: https://github.com/nodejs/node/pull/9615 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
This commit is contained in:
parent
ca86aa5323
commit
75cdc895ec
@ -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
|
||||
`scatter.js`).
|
||||
|
||||
### 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 @@ Benchmark.prototype.report = function(rate, elapsed) {
|
||||
type: 'report'
|
||||
});
|
||||
};
|
||||
|
||||
exports.v8ForceOptimization = function(method) {
|
||||
if (typeof method !== 'function')
|
||||
return;
|
||||
|
||||
const v8 = require('v8');
|
||||
v8.setFlagsFromString('--allow_natives_syntax');
|
||||
|
||||
const args = Array.prototype.slice.call(arguments, 1);
|
||||
method.apply(null, args);
|
||||
eval('%OptimizeFunctionOnNextCall(method)');
|
||||
method.apply(null, args);
|
||||
return eval('%GetOptimizationStatus(method)');
|
||||
};
|
||||
|
Loading…
x
Reference in New Issue
Block a user