Add Nutrient benchmark

JetStreamDriver.js

@@ -2304,7 +2304,22 @@ let BENCHMARKS = [
         iterations: 15,
         worstCaseCount: 2,
         tags: ["Default", "Wasm", "dotnet"],
-    })
+    }),
+    new WasmEMCCBenchmark({
+        name: "nutrient-wasm",
+        files: [
+            "./wasm/nutrient/helper.js",
+            "./wasm/nutrient/build/nutrient-viewer.wasm.js",
+            "./wasm/nutrient/benchmark.js",
+        ],
+        preload: {
+            pdfDocument: "./wasm/nutrient/assets/example.pdf",
+            wasmBinary: "./wasm/nutrient/build/nutrient-viewer.wasm",
+            annotations: "./wasm/nutrient/assets/annotations.json"
+        },
+        iterations: 30,
+        tags: ["Wasm"],
+    }),
 ];
 
 // FIXME: figure out what to do this these benchmarks.

in-depth.html

@@ -333,6 +333,14 @@ <h3>
          Source code: <a href="RexBench/OfflineAssembler/parser.js">OfflineAssembler.js</a>
         </dd>
 
+        <dt id="nutrient-wasm">nutrient-wasm</dt>
+        <dd>
+         Tests the <a href="https://www.nutrient.io/sdk/web">Nutrient Web SDK</a>, a client-side PDF framework that runs in the browser using WebAssembly.
+         This benchmark loads a PDF document, renders a page, creates text annotations, and renders the annotations.
+         It stresses WebAssembly performance and the interaction between JavaScript and WebAssembly for complex document processing operations.
+         Source code: <a href="wasm/nutrient/benchmark.js">benchmark.js</a>
+        </dd>
+
         <dt id="octane-code-load">octane-code-load</dt>
         <dd>
          Test of code load speed of the jQuery and Closure libraries. Because this test allows