‹ BackHN Continuity

Thread

Performance Improvements in .NET 11

349 points · 112 comments · soheilpro

  1. mlhpdx · · focus · HN ↗
    Impressive technical work and authorship. My quibble, which seems significant in context, is what happened with AoT?
    1. CurtHagenlocher · · focus · HN ↗
      AoT is still a thing. Presumably a lot of the JIT improvements would also improve the generation of AoT-compiled code.
      1. mlhpdx · · focus · HN ↗
        I hope that’s the case but I’d feel a lot better to see it in print.
        1. rsalus · · focus · HN ↗
          do you mean NativeAoT? it's mentioned a few times in the post
    2. qingcharles · · focus · HN ↗
      It still exists, it's still a bit quirky because of the way you need to match CPU to binary (e.g. some opcode extensions only existing on some CPUs)
    3. kg · · focus · HN ↗
      AoT uses the same codegen (mostly) as the JIT so if you see a JIT improvement it's possible NativeAOT/ilc picked up that improvement too.

      Unless it's a runtime-only optimization, like guarded devirtualization... there's no straightforward way for an AOT compiler to do that without profiling data.

    4. drewnoakes · · focus · HN ↗
      Native AOT is seeing a lot of use within Microsoft products too. Some bits of the .NET SDK use it, and C# Dev Kit (the C# extension for VS Code) uses it extensively in version 11. It brings a lot of performance to .NET.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.