Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
hooraybuffer's profile
Peter Marshall
Peter Marshall
Peter Marshall
@hooraybuffer

Tweets

Peter Marshall

@hooraybuffer

Engineer on @chromedevtools (and occasionally @v8js)

Munich, Bavaria
Joined December 2015

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. chrisguttandin‏ @chrisguttandin 29 Sep 2018
      • Report Tweet
      • Report NetzDG Violation

      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?

      2 replies 0 retweets 1 like
    2. Mathias Bynens‏Verified account @mathias 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @chrisguttandin @ChromiumDev

      What are you measuring exactly, and how? Either way, *summons @hooraybuffer*

      1 reply 0 retweets 1 like
    3. Peter Marshall‏ @hooraybuffer 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @mathias @chrisguttandin @ChromiumDev

      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 …

      1 reply 0 retweets 2 likes
    4. chrisguttandin‏ @chrisguttandin 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hooraybuffer @mathias @ChromiumDev

      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.

      1 reply 0 retweets 0 likes
    5. chrisguttandin‏ @chrisguttandin 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @chrisguttandin @hooraybuffer and

      Thanks for the link @hooraybuffer . Do I understand that correctly that v8 will now use pre-initialized memory? What happens if (for whatever crazy reason) there is no pre-initialized memory left to use?

      1 reply 0 retweets 0 likes
    6. Peter Marshall‏ @hooraybuffer 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @chrisguttandin @mathias @ChromiumDev

      v8 when embedded in Chromium uses the pre-initialized memory, yes. We get the zeroed pages from the OS, so it will just zero the page on demand (essentially as slow as memset) if there is no more pre-initialized memory left.

      1 reply 0 retweets 0 likes
    7. chrisguttandin‏ @chrisguttandin 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hooraybuffer @mathias @ChromiumDev

      It might be a stupid question, but is this likely to happen or is it almost impossible to run out of pre-initialized memory? I’m asking because I wonder if I should deprecate my async-array-buffer package or not.

      1 reply 0 retweets 0 likes
    8. Peter Marshall‏ @hooraybuffer 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @chrisguttandin @mathias @ChromiumDev

      I think it will always be faster or the same speed without the workers now, for chromium. In Node.js, the allocator calls system calloc() directly so it depends on the system allocator, but I suspect that is also faster. If not, we should fix it there too, so it's fast by default

      1 reply 0 retweets 0 likes
    9. chrisguttandin‏ @chrisguttandin 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @hooraybuffer @mathias @ChromiumDev

      Thanks a lot. I guess I have to come up with a clever way to detect if the worker-workaround (TM) is needed or not. Hopefully without doing any browser sniffing. At least Safari (I have not tested Edge) has still problems with allocating large ArrayBuffers.

      2 replies 0 retweets 0 likes
    10. chrisguttandin‏ @chrisguttandin 5 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @chrisguttandin @hooraybuffer and

      The idea is to free the garbage collection of the main thread from taking care of that ArrayBuffer and let the worker do it without causing jank on the main thread. I was never able to come up with a test which verifies that this is a good idea. I guess you know if it is or not.

      1 reply 0 retweets 0 likes
      Peter Marshall‏ @hooraybuffer 8 Oct 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @chrisguttandin @mathias @ChromiumDev

      It's probably not worth it - we already process ArrayBuffers in parallel during GC and then we put the backing store pointers onto a queue to be released on a background thread. For a few very large buffers, the cost is minimal. Millions of tiny buffers might be different.

      2:33 AM - 8 Oct 2018
      1 reply 0 retweets 0 likes
        1. chrisguttandin‏ @chrisguttandin 8 Oct 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @hooraybuffer @mathias @ChromiumDev

          Thanks a lot for explaining this to me.

          0 replies 0 retweets 0 likes
          Thanks. Twitter will use this to make your timeline better. Undo
          Undo

      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.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info