Good day!
I've got a geoprocessing service up and running, it works well but it's way slow. It can take up to 40 seconds to run and for a general public website, that is hard to accept. Basically, the process goes like this :
1) Use Select By Attributes on a source layer to find a limited number of features(1-3 usually)
2) Buffer the found features (usually 10-500 kilometers)
3) Use the buffers in a Select By Location To find intersected features on other layers ( usually 1-3 target layers)
4) output the selected features and buffers
The culprits in the process are the Select By Attributes and the Buffer operation. They usually requires around 10-15 seconds and 15-25 seconds respectively, to complete. Is there anything I can do to speed things up?
In the worst case scenario, the source data is a large amount of Postal Codes (over a million records) and I know this slows things down. The table is indexed though and I don't know what else I can do to help with this table.
Any help is appreciated!
Bruno
I've got a geoprocessing service up and running, it works well but it's way slow. It can take up to 40 seconds to run and for a general public website, that is hard to accept. Basically, the process goes like this :
1) Use Select By Attributes on a source layer to find a limited number of features(1-3 usually)
2) Buffer the found features (usually 10-500 kilometers)
3) Use the buffers in a Select By Location To find intersected features on other layers ( usually 1-3 target layers)
4) output the selected features and buffers
The culprits in the process are the Select By Attributes and the Buffer operation. They usually requires around 10-15 seconds and 15-25 seconds respectively, to complete. Is there anything I can do to speed things up?
In the worst case scenario, the source data is a large amount of Postal Codes (over a million records) and I know this slows things down. The table is indexed though and I don't know what else I can do to help with this table.
Any help is appreciated!
Bruno