Performance Factors
To supplement the general enterprise GIS performance factors listed under Application Performance Considerations the following are typical performance factors impacting Rich Client Applications:
| Factor | Impact* | Considerations |
|---|---|---|
|
Hardware Infrastructure |
High |
CPU speed and network latency |
|
Application Customization |
Medium | Complexity of functionality, integration with other business systems |
| Extensions | High | Client side ESRI extensions, 3rd party applications and integrations |
| ArcMap Document | High | Scale dependency, number of layers, symbology complexity, map projection on the fly, layer definition queries, spatial views, raster layer |
| ArcGIS Services (e.g. GeoProcessing) |
High | As Rich Client applications make use of services such as Geoprocessing, the performance profile of those services heavily influences the performance of the application. |
| Data Sources | Medium | Data format choice (DBMS, fGDB, shapefile, SDC; storage types, spatial indices |
*Where High implies a high impact, positive or negative, on overall performance
Tuning and Optimization
Tuning typically involves optimization of the following areas:
- Optimize ArcMap documents
- Optimize data sources
- Reduce number of requests to the server
- Reduce number of fetched features
Scalability Strategy
Scalabilty typically involves scaling out and up the following components:
- ArcGIS Server SOC processes and machines
- Scale up – select a bigger server or add more resources
- Scale out -- add more SOC machines, incorporate load balancing, etc.
- Data sources
- Scale up – select a bigger server or add more resources
- DBMS clustering solutions, e.g. Oracle RAC