chore: move benchmarks to file

Author: nbbeeken

test/bench/custom/benchmarks.mjs

@@ -0,0 +1,20 @@
+/* eslint-disable strict */
+import { BSON } from '../../../lib/bson.mjs';
+
+const ObjectId_isValid = [
+  function objectid_isvalid_strlen() {
+    BSON.ObjectId.isValid('a');
+  },
+  function objectid_isvalid_bestcase_false() {
+    BSON.ObjectId.isValid('g6e84ebdc96f4c0772f0cbbf');
+  },
+  function objectid_isvalid_worstcase_false() {
+    BSON.ObjectId.isValid('66e84ebdc96f4c0772f0cbbg');
+  },
+  function objectid_isvalid_true() {
+    BSON.ObjectId.isValid('66e84ebdc96f4c0772f0cbbf');
+  }
+];
+
+// Add benchmarks here:
+export const benchmarks = [...ObjectId_isValid];

test/bench/custom/main.mjs

@@ -4,7 +4,7 @@ import util from 'node:util';
 import fs from 'node:fs';
 import os from 'node:os';
 import benchmark from 'benchmark';
-import { BSON } from '../../../lib/bson.mjs';
+import { benchmarks } from './benchmarks.mjs';
 
 const hw = os.cpus();
 const ram = os.totalmem() / 1024 ** 3;
@@ -22,26 +22,9 @@ console.log(systemInfo());
 
 const suite = new benchmark.Suite();
 
-benchmark.options = {
-  async: false,
-  defer: false,
-  initCount: 1000,
-  minSamples: 1000
-};
+for (const bench of benchmarks) suite.add(bench.name, bench);
 
 suite
-  .add('objectid_isvalid_strlen', function objectid_isvalid_strlen() {
-    BSON.ObjectId.isValid('a');
-  })
-  .add('objectid_isvalid_bestcase_false', function objectid_isvalid_bestcase_false() {
-    BSON.ObjectId.isValid('g6e84ebdc96f4c0772f0cbbf');
-  })
-  .add('objectid_isvalid_worstcase_false', function objectid_isvalid_worstcase_false() {
-    BSON.ObjectId.isValid('66e84ebdc96f4c0772f0cbbg');
-  })
-  .add('objectid_isvalid_true', function objectid_isvalid_true() {
-    BSON.ObjectId.isValid('66e84ebdc96f4c0772f0cbbf');
-  })
   .on('cycle', function logBenchmark(event) {
     console.log(String(event.target));
   })

test/bench/custom/readme.md

@@ -4,16 +4,21 @@ In this directory are tests for code paths not covered by our spec or granular (
 
 ## How to write your own
 
-In `main.mjs` call the `.add` function and pass it an underscore concatenated descriptive title.
-Try to fit the title into the format of: "subject area", "method or function" "test case that is being covered" (Ex. `objectid_isvalid_bestcase_false`).
-Copy the title to the name of the function to assist with debugging and flamegraph capturing.
+In `benchmarks.mjs` add a new test to an existing array or make a new array for a new subject area.
+Try to fit the name of the function into the format of: "subject area", "method or function" "test case that is being covered" (Ex. `objectid_isvalid_bestcase_false`).
+Make sure your test is added to the `benchmarks` export.
 
 ### Example
 
 ```js
-.add('subject_function_testcase', function subject_function_testcase() {
-  BSON.ObjectId.isValid('g6e84ebdc96f4c0772f0cbbf');
-})
+const ObjectId_isValid = [
+  function objectid_isvalid_strlen() {
+    BSON.ObjectId.isValid('a');
+  },
+  // ...
+];
+
+export const benchmarks = [...ObjectId_isValid];
 ```
 
 ## Output