Performance of geoprocessing

Discussion created by jack@freotech on Jul 3, 2017
Latest reply on Sep 30, 2019 by nahmed-esristaff

I am building an add-in for pro using pro sdk 2.0; The add-in reads a specific funky formatted file of point data, creates as point feature layer in local file gdb and symbolises as a feature layer according to metadata in source file;

All working, but users complaining that it's pretty slow : (1k points taking over 40-50 secs on a reasonably powered development machine)
So I want to check whether there is a better approach than this one that I am taking :


1) Using : Geoprocessing.ExecuteToolAsync("CreateFeatureclass_management"...) to create the new, empty feature layer
Time taken : 13-15 secs

2) Add 6 fields to the schema using : Geoprocessing.ExecuteToolAsync("AddField_management", args);
Time taken : 15+ secs

3) Add point features and populate attribute values for 1k points, 6 attributes
Time taken : 2-5 secs

4) Apply unique value based Symbology
Time taken : 2-4 secs

The schema & symbology change with every import so template layers not a solution.


Any ideas?