One of my first larger projects, for instance, involved a lot of data, and I used ADO.NET to construct the access layer. This made up anywhere from a quarter to a third of the entire project.
I could get rid of almost all of that because to my experience with the EF today! Just a lot of the intricate code I manually built is now absolutely unnecessary. Thousands of lines are involved here.
This implies that after the second time, code is executed significantly more quickly. However, you won't benefit from such initializations if you simply run your EF queries once.
You might attempt to make some improvements in a real-world application, such as by utilizing Collected Questions. This will greatly improve your performance because your queries will only need to be prepared and compiled once rather than every time you run them.