DavidObando

user stats

Member SinceFebruary 20, 2012
Last VisitJuly 23, 2014

Contact

developer for

Entity Framework

DavidObando

personal statement

Software developer for Microsoft. Collaborating with the Entity Framework team, especially on the performance and stress fronts.
Twitter: @DavidObando

activity stream

July 7, 2014 - Entity Framework: Closed work item: [Performance]: Slow UpdateEntitySetMapping!

July 7, 2014 - Entity Framework: Modified work item: [Performance]: Slow UpdateEntitySetMapping!

June 26, 2014 - Entity Framework: Modified work item: [Performance] Lower the cost of building code first models

June 26, 2014 - Entity Framework: Modified work item: [Performance]: Slow UpdateEntitySetMapping!

June 26, 2014 - Entity Framework: Commented work item: [Performance]: Slow UpdateEntitySetMapping!

June 26, 2014 - Entity Framework: Modified work item: [Performance]: Slow UpdateEntitySetMapping!

June 26, 2014 - Entity Framework: Modified work item: Sql 2012 tests running and failing when Sql Express is a previous version

June 26, 2014 - Entity Framework: Modified work item: Sql 2012 tests running and failing when Sql Express is a previous version

June 26, 2014 - Entity Framework: Created work item: Sql 2012 tests running and failing when Sql Express is a previous version

June 26, 2014 - Entity Framework: Committed 4851b840e87c35678698efddf1f067f10a532f30, Second cup of coffee - Fix for 2341 After submitting a fix for #2341 with changeset 35835b580fb we detected a threading issue with the entity set mappings cache. The fix is to localize the lock and the cache at the metadata workspace level. This also looks cleaner on the InternalContext side since there's no real need to keep a reference to the mapping dictionary there. The access to the metadata workspace through the ObjectContext has also been studied in order to make sure we're not initializing the ObjectContext when it's not needed. It looks like the change is safe. All tests are passing.