From a310c95e593bad31c77b0d9f079d355aedfed006 Mon Sep 17 00:00:00 2001
From: Uttam Pawar <uttam.c.pawar@intel.com>
Date: Tue, 22 Jan 2019 11:09:18 -0800
Subject: [PATCH] benchmarking: fix runtime regression for require.cache (#257)

Reported regression was due to underlying runner.runBenchmarks()
function. Workaround is to revert the order of functions require.new
and require.cache.

PR-URL: https://github.com/nodejs/benchmarking/pull/257
Fixes: https://github.com/nodejs/benchmarking/issues/202
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
---
 experimental/benchmarks/node-api/require/require.perf.js | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/experimental/benchmarks/node-api/require/require.perf.js b/experimental/benchmarks/node-api/require/require.perf.js
index bbd0104..7b66b58 100644
--- a/experimental/benchmarks/node-api/require/require.perf.js
+++ b/experimental/benchmarks/node-api/require/require.perf.js
@@ -8,12 +8,12 @@ if (module === require.main) {
 }
 
 function runBenchmarks(count) {
-    runner.runBenchmarks('require.new', function(suite) {
-        runner.buildNTests(count, 'require.new', suite, newRequire);
-    });
     runner.runBenchmarks('require.cached', function(suite) {
         runner.buildNTests(count, 'require.cached', suite, cachedRequire);
     });
+    runner.runBenchmarks('require.new', function(suite) {
+        runner.buildNTests(count, 'require.new', suite, newRequire);
+    });
 }
 
 module.exports = runBenchmarks;