{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibzarlxsrg5cleasagkps34um2zorovuncpi55bc3mxxwst2feyjq",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mgnvaq5et4x2"
  },
  "path": "/viewtopic.php?t=33224&p=270956#p270956",
  "publishedAt": "2026-03-09T22:09:33.000Z",
  "site": "http://forum.palemoon.org",
  "tags": [
    "https://xref.palemoon.org/goanna-centra ... amping.cpp"
  ],
  "textContent": "The limited precision in JavaScript is entirely on purpose for security reasons. Multiple side-channel attacks exist that could use high-accuracy timers.\nCurrently, we clamp performance timers to a granularity of 2 ms. See https://xref.palemoon.org/goanna-centra ... amping.cpp\nDepending on what you're trying to measure, you might also be limited to the refresh driver ticking over which would explain the 16 ms (which is ~60 Hz)\n\n* * *",
  "title": "Browser Support • Re: Measuring JavaScript execution time",
  "updatedAt": "2026-03-09T22:09:33.000Z"
}