Poor Performance of Entity Framework over simple queries using Postgresql

Question

In my new project I am keen to use .NET Entity Framework on Postgresql. So I first compared the performance of Entity Framework with simple SQL query. For this I developed a sample desktop application and ran it in both the modes, viz. with Entity Framework & with simple SQL query, in multi-threaded environment. I found that the performance of Entity Framework is 50% lower than that of SQL call. I am using NPGSQL for both the cases.

Performance is the critical success factor for my application and it is serving approximately 250-300 requests per second.

Please suggest whether I should go for Entity Framework or not. Or is there any tips and tricks for improving performance of EF to inline with simple SQL Calls. I am using .NET Framework 4.5.

Please read stackoverflow.com/tags/postgresql-performance/info and edit your PostgreSQL version, explain analyze results, exact query text, etc into the question. Comment here when you're done. — Craig Ringer, Commented Jun 11, 2013 at 12:46
There is no issue in PostgreSQl performance. In our experiment also we got better performance with SQL calls than with the Entity Framework. PostgreSQL version is 9.2.3. — Amit Kumar Jain, Commented Jun 11, 2013 at 13:05
OK... so what's different, then? Are the queries different? It's kind of hard to tell if you don't show the queries.. — Craig Ringer, Commented Jun 11, 2013 at 13:33
use an ORM (whatever it might be) when performance is the "Key point" looks like a nonsense. It's much (much) better for maintenability purposes, not for performance. — Raphaël Althaus, Commented Jun 11, 2013 at 13:33
@Raphaël Although I gave +1 to your comment I don't think it is much (much) better for maintenability because when thinks don't work as expected you must deal with a thick and opaque layer of software between you and the DB. — Clodoaldo Neto, Commented Jun 11, 2013 at 15:36

Chris Travers · Accepted Answer · 2013-10-26 05:34:34Z

0

In general, my experience is that there is a significant performance cost to moving away from hand-tuned SQL. The reason is that entity frameworks often don't have access to the understanding regarding what you really need or want. If performance is critical, there may still be some use cases for ORMs but in general you really need to be able to drop to SQL any time you are doing something beyond the simplest queries.

answered Oct 26, 2013 at 5:34

Chris Travers

26.6k6 gold badges70 silver badges191 bronze badges

Add a comment |

Collectives™ on Stack Overflow

Poor Performance of Entity Framework over simple queries using Postgresql

1 Answer 1

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Your Answer

Sign up or log in

Post as a guest

Related