I suggest you ...

Increase performance of Importing Entities (and related actions)

I've ran into quite a bit of performance issues when importing entities between Entity Managers. The main bottleneck seems to be the deep cloning of the EntityCacheState which uses the DataContractSerializer. This ends up being a pretty heavyweight step if you only need to move a coupe of entities to a new Entity Manager.

There have been other performance problems related to this same behavior.

See the following forum thread for more details: http://www.ideablade.com/forum/forum_posts.asp?TID=3978&KW=&PID=15842&title=performance-issues-with-importentities

13 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Stephen McDaniel shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
completed  ·  AdminJosh Otis (Admin, IdeaBlade) responded  · 

The 7.2 releases improves performance when calling EntityManager.ImportEntities, and of the EntityCacheState when calling CacheStateManager.GetCacheState, RestoreCacheState and Merge.

This improvement is due to a change in the “deep cloning” methodology used by DevForce, and also affects 2-tier EntityManager.SaveChanges calls. [F2137]

This change may be breaking to some applications; see the Breaking Changes section of the release notes for more info:

http://drc.ideablade.com/devforce-2012/bin/view/Documentation/release-notes#H7.2.0

2 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Stephen McDaniel commented  ·   ·  Flag as inappropriate

    We are still on 2010 and might not be upgrading for a little while so we'd vote for the changes to make their way back to 2010. Thanks!

  • Kim Johnson commented  ·   ·  Flag as inappropriate

    We've addressed this in the coming release of DevForce 2012. We may back port to DevForce 2010 if there's enough demand.

Feedback and Knowledge Base