AnsweredAssumed Answered

Performance of EditOperation.ExecuteAsync() operations

Question asked by jack@freotech on Jul 11, 2017
Latest reply on Jul 13, 2017 by cmacleod-esristaff

Is there a known issue with performance of edit operations in V2 ?


I'm adding thousands of points to a filegeodb Point feature class
Using  a EditOperation.Create()  & MapPointBuilder.CreateMapPoint().


In v1.4 adding 3k points , the EditOp.ExecuteAsync() took 9 secs to execute,

Same code in v2.0 is now taking 70 secs.

Also, it now seems to scale poorly with larger datasets.


So for a more realistic operation of 50k points  is now taking 35 minutes !


Can anyone shed light on this ? is there a better way to be doing this ?