Performance tuning an Object-Relational Mapper (ORM)

886 views

Published on

ORMs have become a standard tool, though they can shield us from thinking about what's really happening with our database. It is easy and common to inadvertently have the ORM inefficiently interact with the database, if you're not aware of how key concepts should be applied in different scenarios. Some of the most common performance problems in business applications today stem from misuse of the ORM. We'll go over key concepts to be aware of, that apply to the Entity Framework and Nhibernate, such as table mapping strategies and lazy/eager loading scenarios. We'll also cover simple profiling to get at the heart of ORM performance issues on a .NET project.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
886
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Performance tuning an Object-Relational Mapper (ORM)

  1. 1. Performance Tuning an Object-Relational Mapper Key concepts and approaches
  2. 2. ORMs are useful
  3. 3. Your messy code
  4. 4. My slick ORM
  5. 5. It’s not that easy
  6. 6. IMPACT
  7. 7. #ORMHate
  8. 8. Why care about how they work?
  9. 9. Why care about performance issues?
  10. 10. The main performance concerns
  11. 11. Too little Lazy. Too lazy.
  12. 12. Too long Elapsed time.
  13. 13. Too much Eager. Too eager.
  14. 14. Situations Grids
  15. 15. 1. Profile Common Scenarios
  16. 16. Tools Profilers Tracing (i.e. EFTracingProvider) LinqPad Log
  17. 17. Free Profilers Down to business
  18. 18. Premium Profilers See ORM contexts Code that generates SQL easier to see Bells & whistles (query plans, rows,
  19. 19. 2. Optimize queries
  20. 20. 3. Eager/lazy settings
  21. 21. 4. And more

×