Hi Michal. Well, from my own perspective, the EF queries are the default without AsNoTracking, and we tried to show a comparison between the two default queries. By default EF Core is tracking changes and we didn’t do anything to improve a default Dapper query. Also, this article is not strictly about the performance of the two, the performance is just one of the differences, and again, as we stated, there are techniques that we can add to EF Core queries to improve the speed. I perfectly agree that applying AsNoTracking will speed up the query, and now, when I talk to you about it, I will probably run the test with AsNoTracking and post it in the article, because why not. If this will add a clearer picture of the performance differences between the two, I am more than happy to add that.

I would argue that not applying AsNoTracking is a serious missconfiguration of your test. If you don’t add it the whole test is not fair. It is not an optimization technique, it’s just configuration of the data query.

If you want to compare the features between framework you should use the code equivalent between them. Only then the test is fair and make any sense.

Hi Michal. You are correct, but please read the whole thing and you will see that we explicitly mentioned that. Like here: “That said, this is a simple example as there are many variables that can affect EF Core queries (as we already mentioned) and those results can be much faster.”, and also the section we are mentioning in the sentence I just quoted: “However, it offers several performance optimization techniques, including caching and change tracking, which can enhance overall performance.”