Performance Factors
To supplement the general enterprise GIS performance factors listed under Application Performance Considerations, the following are typical performance factors impacting Web Applications:
| Factor | Impact* | Considerations |
|---|---|---|
|
Hardware Infrastructure |
High |
CPU and disk configuration characteristics, network bandwidth and latency assessments. |
|
Flex API |
High |
Application configuration and complexity |
|
Silver Light API |
High |
Application configuration and complexity |
|
JavaScript API |
High |
Application configuration and complexity |
|
.Net ADF |
Medium |
Application configuration and complexity |
|
Java ADF |
Medium |
Application configuration and complexity |
|
ArcGIS Services |
High |
Map Service document characteristics including dynamic versus cached data sources, and symbology; Geoprocessing Services characteristics including data simplification, index use, and layer files; Image Service raster data types, Geocoding and Globe Services including address locator types, Mobile Services including data update postings and service cache size and Geodata Services including version maintenance, replication approaches and data model requirements |
|
ArcGIS Configuration |
Medium |
Server object manager (SOM) and container (SOC) machine configuration, web service handlers, and virtual directory use. MIME and URL, and security strategies. |
|
Data Sources |
Medium |
Data source storage types, format, data location, and database configuration and maintenance routines. Evaluate use of operational layers, cache basemap layers, and image raster types. |
*Where High implies a high impact, positive or negative, on overall performance
Map service features can be displayed in more than one way, either using export map or query task combine with a browser graphic layer. Each method has different performance and scalability characteristics when displaying features for a given map extent:
| Category | Performance | Scalability |
|---|---|---|
| Map Service | High | High |
| Query task | High (For small number of features) | Low (default limit set to 500 features) |
Tuning and Optimization
Tuning typically involves optimization of the following areas:
- ADF Web Applications
- Reduce single user memory requirements
- Reduce callbacks to the server
- Consider storing UI state in the page
- Flex and Sliverlight Applications
- Consider latency and bandwidth when requesting data from a remote server
- Consider stateless applications whenever possible
- Reduce callbacks to the server
Scalability Strategy
Scalabilty typically involves scaling out and up the following components:
- Scaling out web server (web server farm)
- Scaling out ArcGIS Server SOM (multiple SOM)
- Scaling out ArcGIS Server SOC (SOC server farm)
- Data sources
Tools
Related Links
- MS Open Source Web Application Architecture Guidance
- ESRI Performance Tips for .NET Web Applications
- ESRI Performance Tips for Java Web Applications
- Tuning .NET Application Performance
- Improving .NET Application Performance and Scalability