Hi @ChromiumDev, previously code like `new ArrayBuffer(LARGE_NUMBER)` took several hundred milliseconds to execute. With todays Canary it doesn’t even take a single millisecond. How is that possible?
-
-
We used a special allocator for ArrayBuffer memory which didn't support pre-initialized memory. Now it does. And it's way fast! We don't have to memset the uninitialized memory anymore --> https://bugs.chromium.org/p/chromium/issues/detail?id=864462 …
-
Some time ago I noticed that it can (sometimes) take some time to allocate an ArrayBuffer (or TypedArray). To avoid any delay on the main thread I created https://github.com/chrisguttandin/async-array-buffer … . It can be used to allocate an ArrayBuffer in a worker. It then sends it back as a transferable.
- 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.