6 ms·

Everything is great. Only why from the introduction Ignition in Chrome 59 (2017-06-05) and resignation from V8 with Full-codegen, I have been recording terrible

• cztomsik 8y ago
  I love that project! BTW: how are other browsers?
• lbenes 8y ago
  Have you reported these performance regressions on their bug tracker?[1] I can't find it. Just time for the kernel to boot or you measuring something else? In my experience, they have been quite responsive to quality reports. Like Mozilla, they have many tools to assist QA.[2] [1] https://bugs.chromium.org/p/chromium/issues/list https://bugs.chromium.org/p/chromium/issues/list [2] https://www.chromium.org/developers/bisect-builds-py https://www.chromium.org/developers/bisect-builds-py
  • grapeli23 8y ago
    Initially, it seemed to be a temporary regression. Later that it may be related to Meltdown/Spectre mitigations. Currently, it is well-known to developers and remains patiently waiting for improvement. https://bugs.chromium.org/p/chromium/issues/detail?id=827497#c4 https://bugs.chromium.org/p/chromium/issues/detail?id=827497...
    • lbenes 8y ago
      From your report on the bug tracker: > This is a non-regression issue as it is observed from M60 old builds. No mention of the regression described here. If this is an issue you care about, I suggest you check out the bisect-builds-py tool I linked to.
• Leszek 8y ago
  It'd be interesting to revisit that project with wasm rather than asm.js.