benchmark: increase process priority

to try to avoid involuntary context switches

Author: yaacovCR

.github/workflows/cmd-run-benchmark.yml

@@ -33,7 +33,7 @@ jobs:
 
       - name: Run Benchmark
         run: |
-          npm run benchmark -- --revs HEAD BASE
+          sudo npm run benchmark -- --revs HEAD BASE
 
       - name: Create replyMessage
         uses: actions/github-script@v6

resources/benchmark.ts

@@ -381,9 +381,12 @@ function sampleModule(modulePath: string): BenchmarkSample {
 
   const sampleCode = `
     import fs from 'node:fs';
+    import os from 'node:os';
 
     import { benchmark } from '${moduleURL}';
 
+    os.setPriority(os.constants.priority.PRIORITY_HIGHEST);
+
     // warm up, it looks like 7 is a magic number to reliably trigger JIT
     benchmark.measure();
     benchmark.measure();