Performance Improvements in .NET 11

(devblogs.microsoft.com)

98 points | by soheilpro 1 day ago

6 comments

  • kristianp 13 minutes ago
    > The sections that follow are full of real improvements. A bounds check removed, an allocation that no longer happens,

    Annoyingly the.net blog seems to have started to use LLMs to write their copy. Using "real" twice in one paragraph - do LLMs do that? Lots of commas is a tell for me.

    > This is a long one. It’s meant to be. Grab your hot beverage of choice, settle in, and let’s turn it up.

    Ugh.

    • pestkranker 5 minutes ago
      These comments about potential LLM usage are so boring. Stephen is doing this kind of blog post since 6+ years. They all look the same. Read it! It’s very good. Performance deep dives with this kind of quality are rare.
  • gerdesj 13 minutes ago
    Spinal Tap's "put it up to 11". My laptop (Kubuntu) has volume controls that allow me to override 100% and take it to 150%.

    I can wind it up to 15! \||/ (is there an official ASCII art four finger devil's horns)

  • adzm 1 day ago
    Runtime async is certainly an interesting development. Really excited to see how this plays out.
  • eterm 19 minutes ago
    This has been very noticeable in some benchmarks I've been doing lately, I'm looking forward to the full release.
  • pjmlp 1 day ago
    Ah the traditional browser stress test from the .NET team. :)

    Joke aside, yet another interesting read of all little improvements that go across all the runtime, and very much appreciated that they put out the effort to go through this detail level.

  • equasar 1 day ago
    Thanks Stephen for this, it is very rewarding to read something very technical that is not AI slop these days.