@onimaxxing/worldgen 0.18.0 → 0.18.1

package/index.js

@@ -42,7 +42,15 @@ function _requireInit(method) {
  *   passed through to wasm-bindgen's init.
  * @param {number | 'auto' | 'serial'} [opts.threads='auto'] `'serial'`
  *   forces the serial build; a number sets an explicit rayon worker
- *   count; `'auto'` uses `navigator.hardwareConcurrency`.
+ *   count; `'auto'` uses `min(navigator.hardwareConcurrency, 4)`.
+ *   The clamp is deliberate: Rust's wasm allocator takes a single
+ *   global lock, and worldgen's layout phase is allocation-heavy, so
+ *   many workers generating multiple worlds concurrently serialize on
+ *   malloc and can erase the parallel win entirely (browser A/B on a
+ *   16-thread host: 8-world cluster 380 ms at 16 workers ≈ serial;
+ *   ~330 ms at 4; ~285 ms at 2 — while a 1-world coord runs best at
+ *   high counts, ~157 vs ~170 ms). 4 is the compromise that wins on
+ *   both shapes; pass an explicit number to override.
  * @returns {Promise<void>}
  */
 async function init(opts) {
@@ -62,9 +70,12 @@ async function init(opts) {
     }
 
     if (wantParallel && typeof mod.initThreadPool === 'function') {
+      // Clamp 'auto' to 4 workers — see the `threads` doc above
+      // (allocator-lock contention makes high worker counts LOSE on
+      // multi-world clusters).
       const threads = typeof opts?.threads === 'number'
         ? opts.threads
-        : (globalThis.navigator?.hardwareConcurrency ?? 4);
+        : Math.min(globalThis.navigator?.hardwareConcurrency ?? 4, 4);
       await mod.initThreadPool(threads);
     }
 

package/package.json

@@ -2,7 +2,7 @@
   "name": "@onimaxxing/worldgen",
   "type": "module",
   "description": "WASM entry point for ONI worldgen",
-  "version": "0.18.0",
+  "version": "0.18.1",
   "license": "MIT",
   "repository": {
     "type": "git",