While prototyping some model caching changes I noticed that model access perf. (i.e. calling IObjectContextAdapter.ObjectContext) has regressed quite substantially:
AdventureWorks Code First model timings (5000 iterations):
EF5: 16s
EF6: 42s
It looks like the regession is in the InternalContext.ForceOSpaceLoadingForKnownEntityTypes() code path.
Comments: Tested with the latest bits (which have changed significantly in this area) and I am now seeing these times for MonsterModel: EF5: 15s EF6: 5s Recommend that we don't do any more work on this unless the perf suite picks something up.
AdventureWorks Code First model timings (5000 iterations):
EF5: 16s
EF6: 42s
It looks like the regession is in the InternalContext.ForceOSpaceLoadingForKnownEntityTypes() code path.
Comments: Tested with the latest bits (which have changed significantly in this area) and I am now seeing these times for MonsterModel: EF5: 15s EF6: 5s Recommend that we don't do any more work on this unless the perf suite picks something up.