The original thread is on the devil’s website and I don’t want to direct traffic to it, so here’s a link to the tweet instead:
https://twitter.com/davidfowl/status/1671351948640129024?s=46&t=OEG0fcSTxko2ppiL47BW1Q
The original thread is on the devil’s website and I don’t want to direct traffic to it, so here’s a link to the tweet instead:
https://twitter.com/davidfowl/status/1671351948640129024?s=46&t=OEG0fcSTxko2ppiL47BW1Q
Performance limits of LINQ…?
You’re getting nearly the same performance out of loopes generated by LINQ as you would normal for loops.
If you’re referring to LINQ and EF Core, you’re generation SQL with it, not running LINQ. And that query generation is incredibly performant these days (I think EF 7 was something like 5% slower than dapper?).
So luckily you can squeeze a ton of performance out of it!