{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidbvw76zpwtstcmqvib7dthevgilqbtaujffsqju3g4zyzzsezi5q",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mgo3yinj2y42"
  },
  "path": "/viewtopic.php?t=33224&p=270966#p270966",
  "publishedAt": "2026-03-09T22:53:52.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "The common way to more accurately benchmark is to measure runs/s, not raw timing.\ni.e. measure a start time, then run your test in a loop incrementing a counter to keep track of the number of loops performed, until at least end time - start time > 1s (or multiple for accuracy), then just divide the loops run through (counter) by the actual time taken (end - start, adjusted to seconds) to get the benchmark score.\n\nAs for a preference, no, we currently don't have a preference for this. Although we may want to revisit this to make it a bit more fine-grained again as spectre and meltdown have been mitigated and/or are no longer as much of a concern on current hardware.\n\n* * *",
  "title": "Browser Support • Re: Measuring JavaScript execution time",
  "updatedAt": "2026-03-09T22:53:52.000Z"
}