in entity framework

ORM Series : Performance Part I : NHibernate, EF, OpenAccess, XPO Devexpress

In one of my companies on of the first tasks was to create appllication, that will show which ORM will be the best choice for my team ( in terms of performance, support and features). Main focus of this task was performance. My company has a online shop that is generating a huge ammout of queries. This was an important task, because we planned to redesign whole project with ORM in order to improve efficiency and get rid off all the complex stored procedures with business logic.

I selected four popular ORMs (Entity framework, OpenAccess, XPO Devexpress, NHibernate). Each test was ran ten times to reject gross error (values were averaged)

Local machine – Summary



  • Insert, probably you have wondering why single insert record has more time than inserting ten records. Probably its cost of first connection with database. And this problem is not only shown in insert but it’s happend in Update and Delete. The best performance has NHibernate 1 minute and 20 seconds with inserting 10k records! either OpenAccess has scored 1 minute and 39 seconds, opposite site  Entity Framework with 3 minutes and 5 second and it’s the worst score.
  • Update, undeniably, the fastest update has got NHibernate, it has won updating all of values but in the 10k records NHibernate just crushed his competition! 5 second . The worst time has got OpenAccess 1 minute 12 second.
  • Delete, it’s very good example how syntax and features influence in speed of our queries just one ORM reached this horrible time – Entity Framework, there is no something like deleting collection and I was forced to using foreach statement to delete all items in collection (10k)! 3 minutes and 49 seconds. Other ORM done well their job but the best is XPO.



Undoubtedly the best time has NHibernate, it hasn’t lost any category and it won most of them.
After NHibernate, XPO Devexpress ranks in the second position. The worst was Entity Framework it lost the most time and its deleting time is just killing for our database.

EF version :
XPO version :
NHibernate version :
OpenAccess version : 2012.3.1209.1

  • Biegal


    Could you please elaborate more about the environment ?
    What libraries versions have you been using, what is the framework version ?

    • Pawel Sawicz

      I’ll add this informations.

  • Arek Bal

    Giving results without giving out the tests is damnly unscientific.

    • Pawel Sawicz

      sure I’ll give code for few days. 🙂 sorry if you feel resentful.

  • Slawek

    Add pure ADO.NET comparison to see how much all those frameworks do overhead.

    • Pawel Sawicz

      thanks for advice.

  • Pawel

    This is silly. Cost of N CRUD operations in one go gives you false predicition about system performance after introducing concrete ORM.

  • Pingback: Entity Framework – missing feature | Pawel Sawicz .NET blog

  • Carlitos Melgar

    I wonder what’s the result on this if you run it against the current builds??

  • Marco Kummer

    I’ve used XPO for many years, and I would never trade it for EF or NHibernate. It’s like going back to the stone ages. XPO does what I expect from a good ORM: Any schema change that is non-conflicting is simply handled by the ORM; no need for complex SQL script generation. For complex schema changes, XPO offers very useful helper methods, including the simple execution of native SQL statements before and after XPO’s own schema corrections. So as a developer I only have to handle the really complex cases… and if you plan your domain model wisely, you hardly need any breaking changes, only adding of new classes, relations and properties – which are all done automatically by XPO.