{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreigqn4esjdyk56x6brw3cangmnwob52zcyqojvndlfufxsu5a65jbm",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mii2gihbnuj2"
  },
  "path": "/viewtopic.php?t=33281&p=271714#p271714",
  "publishedAt": "2026-04-01T20:23:37.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://repo.palemoon.org/MoonchildProd ... hreads.cpp"
  ],
  "textContent": "> Could there be much more to fast JavaScript crunching than just multi-process?\n\nThere are almost certainly places in a codebase as large as ours where multithreaded performance could be improved without introducing a full multiprocess implementation.\n\nI've been experimenting with this different areas of the codebase looking for improvements. For example, locally I browse on an architecture with no JIT. I've been changing this code in local builds from 1 to 4 (so 4 helper threads instead of 1) and haven't noticed any issues yet: https://repo.palemoon.org/MoonchildProd ... hreads.cpp#\n\nJITLess build means no WASM so I wasn't as worried about it there.\n\nThere's an obvious warning there explaining why we shouldn't do this so we wouldn't want to upstream that change but the difference is somewhat noticeable on my local builds.\n\n* * *",
  "title": "Platform Development • Re: e10s support question",
  "updatedAt": "2026-04-01T20:23:37.000Z"
}