Comparing the performance of Entity Framework Core and SqlDataReader in ASP.NET Core

Erick McCollum | 27 Apr 2021

DISCLAIMER: The opinions expressed on this website are solely my own, and they are not associated with my employer, another person, or another organization in any way. All information on this website is provided "as is," without guarantee or warranty of any kind. Read the full disclaimer here.

When using ASP.NET Core, there are many different possibilities for integrating with a database. Two popular methods to do this are 1) using an object-relational mapper, such as Entity Framework Core, or 2) writing SQL queries directly using a lightweight SQL client class, such as the SqlDataReader class. Each of these methods have their own pros and cons. For more information on these two methods, please find some resources in the “Additional Resources” section at the end of this article.

In this article, I will be comparing the performance of reading SQL data using Entity Framework Core and SqlDataReader.

Note: As you read this article, please keep in mind that this is intended to be a high-level performance comparison, not an in-depth performance analysis.

Performance Test Overview

I will be doing a simple performance comparison using an ASP.NET Core web API application. This web application will be targeting .NET Core v3.1. The source code used in this performance comparison may be found in my GitHub repository at the following link: code-samples/dotnet/EFCoreVsSqlDataReader.

This web API application will interact with a local SQL Server Express Database (hosted within the default Visual Studio LocalDB) named ExampleDb. The ExampleDb database will contain one million records in a single table named ExampleRecords. The web API will expose the following endpoints:

  1. api/EFCore/GetTopRecords
  2. api/EFCore/GetEvenRecords
  3. api/EFCore/GetComplexWhere
  4. api/SqlDataReader/GetTopRecords
  5. api/SqlDataReader/GetEvenRecords
  6. api/SqlDataReader/GetComplexWhere

Each of the above endpoints will perform a different read operation on the ExampleRecords table in the ExampleDb database. Once the read operation has completed, a record will be created in the TimingLogs table. This record in the TimingLogs table will log the amount of time, in milliseconds, that it took to complete that read operation.

I will not go into detail describing each of the queries being performed in the above endpoints. However, if you would like to review and compare the queries for yourself, please feel free to do so. As mentioned, the source code may be found in my GitHub repository at the following link: code-samples/dotnet/EFCoreVsSqlDataReader.

Using PostMan, I will send 51 HTTP requests to each of the above six web API endpoints (for a total of 306 HTTP requests). The first request will serve as a warm-up for the web API endpoint. The following 50 HTTP requests will be used for the purposes of this performance comparison (for a total of 300 HTTP requests). Each of the 51 HTTP requests will be separated by a delay of 500 ms (half of a second).

I understand that this is a very simple performance test. However, as noted above, this is not intended to be an in-depth performance comparison.


Please find the average, maximum, and minimum results of this performance comparison below. Based on the below results, we can see that there is an average performance increase of about 42% when using the SqlDataReader class.

Additional resources

The following resources may also be helpful.

Copyright © 2019

License | Terms & Conditions | Privacy Policy | Disclaimer