Performance penalty with using Beta 3 version of the API

SasaI_

I tested out the performance of the Beta3 API release and I noticed a huge difference in writing and deleting geometries in the database.  I wrote two simple test programs using the Editing sample to write 25k points to a table then delete them.  As my test numbers show, it takes almost 5x as long to Write and Delete the points in the beta3 version than it did in beta2.  Is there a reason there is such a huge difference between the two APIs?

The times from my test programs:

Beta2 version:

Testing with 25,000 points.
Finished inserting rows, time taken: 4.531s
Finished deleting all rows, time taken: 3.371s
Total time taken: 7.904s

Beta3 version:

Testing with 25,000 points.
Finished inserting rows, time taken: 19.388s
Finished deleting all rows, time taken: 18.013s
Total time taken: 37.404s

The testing programs were based on the Editing sample.  They write to the a clean geodatabase/table.  Beta2 version uses the raw buffer (allocate + memcpy) while Beta3 version uses PointShapeBuffer (Setup + GetPoints) for geometry creation.  They both use table.Delete(row) to remove a row.

SasaI_

Thank you for identifying this issue which was also picked up by our own internal performance tests.  We've duplicated the problem and have a solution.  The issue was due to the addition of the IsEditable check to block the modification of features with advanced geodatabase behavior.  The fix will be available in the Final code drop for the File API.

Thank you Lance.  I figured it may have something to do with the IsEditable check, as there was nothing else mentioned in beta3 updates that should have had any effect on the code.  I'm glad its a bug that will be fixed, and not just something we have to live with.