The INSANE performance boost of LINQ in .NET 7

Every place I've work uses LINQ in "hot paths", performance wise I'd label not using LINQ as micro optimization... I would also decline any PR that had one off code already in System.Linq.

Code source, please. Thanks.

Interesting but please talk a little bit slower in your videos to keep up with your english please....

Was wondering why LINQ was so shit. C++ programmer going to C# is a bit underwhelming

Nice. I had the idea to vectorize summing once. Damnit, I could have been the first.

It's unbelievable bro

Sorry, mate. But I tried this case for int and double for .net6 and .net7, and for non-zero array, but randomly generated numbers.
My benchmarking showed no difference between .net6 and .net7, and also between Linq max and onw max.
May be the improvement, what you are talking about is just about the jumping over the zero elements in .net7? That can make this difference in your case.

So, if you try not "int", but "float", you will see some difference. They are more or less equal for .net6, but for .net7 the difference is drastic: float is x10 slower than int.

who interferes to port net 7 code into your own library and use it in .net6 if u have alot of similar linq expressions)

I knew it, after seeing the first benchmarks results that it uses SIMD under the hood now ;-)
SIMD is the best way to optimize any code that relies on mathmatical operations and its results - but only makes sense for medium/large amounts of data. Also you can even filter out values using Vector.ConditionalSelect() which makes it much more versatile.

After I learned Lamda I've been a repeated LINQ abuser. I mean I'd be serving multiple life sentences with how hard I abuse it.

I do the see the link to the post about vector

It isn't 2 times fast or 5 times fast. It is actually insanely fast.

Great news!

very nice - I have a startup that's 99.9% linq as I need to write so much in so little time (not premature the optimization) - and use Sum()/min()/max() a lot.. the move from to 6 was good and my customers always love the performance of my app - but this will just turbocharge my reports/queries - and take a load off the backend!! Whooo hoo.. a perfect upgrade for me.... thanks I will do it over the Christmas 'break'....

PR rejected for using LINQ, WTF... where does this happen lol.

foreach runs over an enumerator, Own version should use for loop

Can we move everything to .NET 7? Apparently, they focused on performance and the results are amazing

Another great video. I'd love to see your approach for a fully dynamic expression tree builder.

Thanks! I've been searching how to get it and this is brilliant :D

Mind blowing 🤯 thank for sharing

so cool, thank you

So the upshot is that they sped up a terribly slow process. Not the game changer it sounded like.

BROTHER, YOU ARE THE BEST!!! You oooh really helped me!! THANK YOU VERY MUCH!

Great.
Is any download size improvement for Blazor wasm with .net 7?

Wow😵

Works good, tnx

Thanks, Nick. Good job.

It's just awesome

Thanks bro that was really helpful

When someone makes something 45 times faster it is generally an indication they didn't care about performance when they first wrote it. The good thing is, this isn't that...

The moment you went to analyze the source code of C# itself was the moment I noped the fuck out

Bro, thx!

Compare Max and Own_Max on simple array not IEnumerable

You should use size is equal to 101 instead of 100. Bcs compiler have an optimizations on even sizes of collections. Creator of dotNet benchmark wrote about this.

This new dotnet 7 method also declares and uses new variables to calculate min/max, while benchmark tests report 0kb allocated. I am so confused

I thought it was a hoax, but everything works!

Madness!

Great, maybe our senior devs will finally let us use LINQ now 🙄

Does this mean LINQ is competitive with Rust's zero cost abstractions?

finally! took them long enough. I've been complaining about the speed since Linq was introduced.

Thank you. It really works 

I'd be interested in 1) Seeing how a foreach compares in performance to a for (int i = 0) situation and 2) seeing the performance of Linq Select and Where

Like

I just brought our legacy application to .net 6 leave me alone with .net 7 🤣😜

he read appres and pack books. after record video :D

I'd be curious to see these benchmark results on various platforms, especially iOS and Android, if the results are similar there then I can't wait for Unity to adopt .NET 7. Although Unity also converts mobile to C++ code, so I wonder if those gains would hold up after that translation.

Muchas gacias por compartir esta infor!