{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifzri4sqncfj65ljm3ziu7kuk5d2gy6azo2phn2i4judfulbmn4x4",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mkpiq7qjbyw2"
  },
  "path": "/viewtopic.php?t=33382&p=273035#p273035",
  "publishedAt": "2026-04-30T09:30:54.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Variable \"threadCount\" is used in other places to determine load distribution. There will be the same logic of “overloading” small processors and “underloading” large ones. It might be worth changing the calculation for allocating “additional load (extra capacity)”?\n\nFor simpler tasks like decompression and the like, that isn't a problem, but parsing/interpreting/compiling is a whole different beast and you can't just arbitrarily \"load it up\".\n\nYou may have missed the point Athenian was trying to make in that cpuCount is already dynamically scaling to the logical processors, and threadCount just adds some extra; you don't necessarily want to scale that up as it doesn't scale linearly in hardware and you'd be disproportionately loading the CPU scheduler if you add more over-capacity on higher core count CPUs, so just having a set amount makes sense there. We were just put on the wrong foot what \"cpu\" and \"thread\" actually means in the code.\n\n* * *",
  "title": "Platform Development • Re: The browser hang with 0 CPU load.",
  "updatedAt": "2026-04-30T09:30:54.000Z"
}