GIS Software Technology (CPT Demos) 41st Edition

From wiki.gis.com
Jump to: navigation, search
Capacity Planning Tool TABLE OF CONTENTS 41st Edition
1. System Design Process (CPT Demos) 41st Edition 2. GIS Software Technology (CPT Demos) 41st Edition 3. Software Performance (CPT Demos) 41st Edition
4. Server Software Performance (CPT Demos) 41st Edition 5. GIS Data Administration (CPT Demos) 41st Edition 6. Network Communications (CPT Demos) 41st Edition
7. Platform Performance (CPT Demos) 41st Edition 9a. GIS Product Architecture (CPT Calculator Demos) 41st Edition 9b. GIS Product Architecture (CPT Design Demos) 41st Edition
10. Performance Management (CPT Demos) 41st Edition 11a. City of Rome Year 1 (CPT Demos) 41st Edition 11b. City of Rome Year 2 (CPT Demos 41st Edition)

Arc17CapacityPlanning0701

Figure A-2.1 ArcGIS shares a global platform for working with maps and geographic information.
ArcGIS shares a variety of software technology patterns available to satisfy enterprise business operational needs and help communities work together to better manage our world. Technology patterns include a broad range of Desktop, Server, and Mobile deployment options. Selecting the right technology is a critical step in the enterprise system design process.

This section shows the available ArcGIS software workflow patterns and how they are represented in the Capacity Planning Tool (CPT). Standard Workflow patterns represented in the CPT include the following:

  • ArcGIS Desktop
- Workstation
- Windows terminal services
  • ArcGIS Server
- Web map services
- Imagery services
  • ArcGIS Mobile
- ArcGIS mobile provisioning and synchronization services

CPT desktop workflows

ArcGIS Desktop provides a variety of deployment options to satisfy your specific business needs. Selecting the right deployment option for each specific user workflow is the primary role of your system design process.

Figure A-2.2 Desktop workflow performance targets are generated from the CPT Calculator tab.

Figure A-2.2 shows the CPT Calculator ArcGIS Desktop software technology selection.

ArcGIS Desktop workflow performance targets are generated from the CPT Calculator tab.

  • Software selections include workstation (wkstn) and Windows Terminal Server (WTS Citrix) workflow architecture patterns (options include direct connect, feature service, and imagery data sources).
  • ArcGIS Desktop includes ArcMap or Pro client application.
  • Map display can be 2D or 3D graphics representation.
  • Density can be vector only or raster image data source.
  • Light, medium, heavy, 2xMedium, 3xMedium, 4xMedium, 5xMedium, …, 10xMedium display complexity settings provide a full range of potential workflow performance targets.
  • DeskDefault display resolution is 1920x1080 pixels.
  • Wkstn and Citrix FSvc software selections include ArcGIS Server feature service data source.
  • Density/Portal VP and RP selections activate registered portal workflows.
Note: Software technology performance factors are discussed in greater detail in Lesson 3: GIS software performance.

Software workflow recipe

The CPT Calculator generates a workflow recipe in cell A3 that identifies the selected Software Technology and Performance Parameters.

  • Software technology selection establishes a workflow profile based on a technology baseline.
  • CPT performance factor selections include software, Desktop, Graphics, density, complexity, %DataCache, resolution, and output. These are the primary workflow performance variables identified during Esri benchmark testing.
  • Changes in the software performance parameters will change the workflow performance targets (service times) based on technology baselines and key parameters established during performance benchmark testing.
Note: The Software technology selection section in the software performance chapter provides more information on selecting appropriate workflow performance targets.


ArcGIS Desktop Standard Workflows

Figure A-2.3 ArcGIS Desktop Standard Workflow performance targets are provided on the CPT Workflow tab.

Figure A-2.3 shows the ArcGIS Desktop workflow patterns available on the CPT Workflow tab. The Workflow tab is the Excel performance target look-up table used for CPT Design.

The most common ArcGIS Desktop workflow patterns are pre-generated from the Calculator tab and included on the Workflow tab as Standard Workflows. Standard workflows are provided for ArcGIS Desktop Workstation and Citrix deployment patterns. Citrix is a generic term used to represent a variety of supported remote desktop deployment patterns.

ArcGIS Desktop Workstation Standard Workflows.

  • AGD wkstn ArcMap 2D V Med 100%Dyn 19x10 Feature. Use for simple ArcMap 2D user desktop workflows. Display and database design follow best practice performance guidelines.
  • AGD wkstn ArcMap 2D V Hvy 100%Dyn 19x10 Feature. Use for standard ArcMap 2D loads that support typical business workflows. Processing loads are 50 percent more than medium complexity workflow.
  • AGD wkstn Pro 2D V Med 100%Dyn 19x10 Feature. Use for simple ArcGIS Pro 2D user desktop workflows. Display and database design follow best practice performance guidelines.
  • AGD wkstn Pro 2D V Hvy 100%Dyn 19x10 Feature. Use for standard ArcGIS Pro 2D user workflow loads. Processing loads are 50 percent more than medium complexity workflow.
  • AGD wkstn FSvc Pro 2D VP Hvy 20%Dyn 19x10 Feature +$$. Use for standard ArcGIS Pro 2D 20% dynamic Portal feature service user workflow loads with ArcGIS Server Data Store data source. Follow best practices for map display and database performance. Display includes mashup with cached tile basemap.
  • AGD wkstn Pro 3D V Med 100%Dyn 19x10 Feature. Use for simple ArcGIS Pro 3D user workflow loads with simple map displays. Display and database design follow best practice performance guidelines.
  • AGD wkstn Pro 3D V Hvy 100%Dyn 19x10 Feature. Use for standard ArcGIS Pro 3D user workflow loads. Processing loads are 50 percent more than medium complexity workflow.
Warning: Medium 3D complexity is based on feature density in a 2D medium workflow. 3D workflow complexity increases with feature density and can be much heavier than a standard 2D workflow

Heavier workflow recipes can be generated from the CPT Calculator and included in your project workflows.

ArcGIS Desktop Citrix Standard Workflows. ArcGIS Desktop application is deployed on a centralized host platform server configuration accessed from a remote client display.

  • AGD Citrix ArcMap 2D V Med 100%Dyn 19x10 ICA. Use for simple ArcMap 2D user desktop workflows with vector only data source. Display and database design follow best practice performance guidelines.
  • AGD Citrix ArcMap 2D V Hvy 100%Dyn 19x10 ICA. Use for standard ArcMap 2D loads that support typical business workflows with vector only data source. Processing loads are 50 percent more than medium complexity workflow.
  • AGD Citrix ArcMap 2D R Med 100%Dyn 19x10 ICA. Use for simple ArcMap 2D user desktop workflows map displays that include an imagery data layer. Display and database design follow best practice performance guidelines.
  • AGD Citrix ArcMap 2D R Hvy 100%Dyn 19x10 ICA. Use for standard ArcMap 2D loads that support typical business workflows with map displays that include an imagery data layer. Processing loads are 50 percent more than medium complexity workflow.
  • AGD Citrix Pro 2D V Med 100%Dyn 19x10 ICA. Use for simple ArcGIS Pro 2D user desktop workflows with vector only data source. Display and database design follow best practice performance guidelines. Host server machine must include properly configured NVIDIA GRID video card.
  • AGD Citrix Pro 2D V Hvy 100%Dyn 19x10 ICA. Use for standard ArcGIS Pro 2D user workflow loads with vector only data source. Processing loads are 50 percent more than medium complexity workflow. Host server machine must include properly configured NVIDIA GRID video card.
  • AGD Citrix Pro 2D R Med 100%Dyn 19x10 ICA. Use for simple ArcGIS Pro 2D user desktop workflows with map displays that include an imagery data layer. Display and database design follow best practice performance guidelines. Host server machine must include properly configured NVIDIA GRID video card.
  • AGD Citrix Pro 2D R Hvy 100%Dyn 19x10 ICA. Use for standard ArcGIS Pro 2D user workflow loads with map displays that include an imagery data layer. Processing loads are 50 percent more than medium complexity workflow. Host server machine must include properly configured NVIDIA GRID video card.
  • AGD Citrix FSvc Pro 2D VP Hvy 20%Dyn 19x10 ICA. Use for standard ArcGIS Pro 2D 20% dynamic Portal feature service user workflow loads with vector only ArcGIS Server Data Store data source. Processing loads are 50 percent more than medium complexity workflow. Display includes mashup with cached tile basemap. Host server machine must include properly configured NVIDIA GRID video card.
  • AGD Citrix FSvc Pro 2D RP Hvy 20%Dyn 19x10 ICA +$$. Use for standard ArcGIS Pro 2D 20% dynamic Portal feature service user workflow loads with vector only ArcGIS Server Data Store data source. Processing loads are 50 percent more than medium complexity workflow. Display includes mashup with cached tile imagery basemap. Host server machine must include properly configured NVIDIA GRID video card.
  • AGD Citrix Pro 3D V Hvy 100%Dyn 19x10 ICA. Use for standard ArcGIS Pro 3D user workflow loads with vector only data source. Processing loads are 50 percent more than medium complexity workflow. Host server machine must include properly configured NVIDIA GRID video card.
  • AGD Citrix Pro 3D R Hvy 100%Dyn 19x10 ICA. Use for standard ArcGIS Pro 3D user workflow loads with map displays that include an imagery data layer. Processing loads are 50 percent more than medium complexity workflow. Host server machine must include properly configured NVIDIA GRID video card.
Warning: Medium 3D complexity is based on feature density in a 2D medium workflow. 3D workflow complexity increases with feature density and can be much heavier than a standard 2D workflow

Heavier workflow recipes can be generated from the CPT Calculator and included in your project workflows.

CPT server workflows

ArcGIS Server includes a broad variety of web clients and service offerings developed to meet your specific workflow needs.

Figure A-2.4 ArcGIS Server workflow performance targets are generated from the CPT Calculator tab.

Figure A-2.4 shows the CPT Calculator ArcGIS Server software technology selections.

ArcGIS Server workflow performance targets are generated from the CPT Calculator tab.

  • ArcGIS Server provides a variety of web mapping applications and map service deployment patterns.
  • The CPT Calculator ArcGIS 10.3 workflows generate performance targets for REST, KML, WMS, SOAP, KMZ, Portal and imagery deployment patterns.
Note: Portal for ArcGIS workflow should be used to identify service loads for client collaboration and sharing activities on a Portal service that do not include access to registered services. Service loads for registered service access are included with the Portal registered service workflow service times. With the Arc17CapacityPlanning0701 release, the PortalShare load is included with the registered services (light loads) which should provide a conservative design without addressing PortalShare loads.


ArcGIS Server standard workflows

Figure A-2.5 ArcGIS Server standard workflow performance targets are provided on the CPT Workflow tab.

Figure A-2.5 shows the ArcGIS Server workflow patterns available on the CPT Workflow tab.

The most common ArcGIS Server workflow patterns are pre-generated from the Calculator tab and included on the Workflow tab as Standard Workflows.

  • AGS REST 2D VP Hvy 100%Dyn 13x7 PNG24. Use for standard map display services with PNG24 output (transparent overlay) registered with a Portal for ArcGIS server. Processing loads are 50 percent more than medium complexity workflow.
  • AGS REST 2D V Med 100%Dyn 13x7 PNG24. Use for simple map display services with PNG24 output (transparent overlay). Display and database design follow best practice performance guidelines.
  • AGS REST 2D V Hvy 100%Dyn 13x7 PNG24. Use for standard map display services with PNG24 output (transparent overlay). Processing loads are 50 percent more than medium complexity workflow.
  • AGS REST 2D V Hvy 100%Dyn 13x7 PNG24 +$$. Use for standard map display services with PNG24 output (transparent overlay) with cached basemap. Processing loads are 50 percent more than medium complexity workflow.
  • AGS REST 2D V Hvy 40%Dyn 13x7 PNG24 +$$. Use for standard map display services with PNG24 output using dynamic business layers (40% dynamic) combined with a cached basemap. Processing loads are 50 percent more than medium complexity workflow.
  • AGS REST 2D V Hvy 20%Dyn 13x7 Feature +$$. Use for feature editing of a limited number of business layers (20% dynamic) registered with Portal for ArcGIS and combined with a cached base map. Processing loads are 50 percent more than medium complexity workflow.
  • AGS Full MapCache. Use with fully cached map or imagery service.
  • AGS PortalShare. Portal for ArcGIS workflow should be used to identify service loads for client collaboration and sharing transactions on a Portal service that do not include access to registered services.
  • AGS KML 2D V Hvy 100%Dyn 13x7 PNG24. Use for standard map display services using KML output capabilities.
  • AGS WMS 2D V Hvy 100%Dyn 13x7 PNG24. Use for standard map display services using WMS output capabilities.
Best Practice: Use the CPT Calculator to complete a workflow analysis for each business use case, and then use the Calculator-generated workflow service times for your design specifications.

Standard workflows provide a reasonable performance target for medium and heavy software deployment use-cases. In most cases, Standard Workflows provide performance targets with adequate margins for your design.

Best Practice: The workflow recipe should be used as design specifications by the service author and software developer to ensure compliance with performance targets during system deployment.
Note: Workflow display complexity is discussed in more detail in Chapter 3: Software Performance.

ArcGIS Server Image Services standard workflows

The most common ArcGIS Server Image Services workflow patterns are pre-generated from the Calculator tab and included on the Workflow tab as Standard Workflows.

  • AGS Imagery 2D R Lite 100%Dyn 19x10 JPEG. Use for image service workflow with pre-processed imagery files (single image). Appropriate when display service scales are aligned with source raster pyramids to avoid resampling or on-the-fly reprojections.
  • AGS Imagery 2D R Med 100%Dyn 19x10 JPEG. Use for standard imagery mosaic dataset workflow with on-the-fly processing. Resampling and on-the-fly reprojections with complex imagery data sets can increase complexity to heavy or higher processing loads.
  • AGS Imagery 2D R Hvy 100%Dyn 19x10 JPEG. Use for standard imagery mosaic dataset workflow with on-the-fly processing with imagery analysis. Resampling and on-the-fly reprojections with complex imagery data sets may increase complexity to higher processing loads.

CPT Mobile Workflows

Mobile GIS supports a range of mobile systems from lightweight devices to PDAs, laptops, smart phones, and tablets.

ArcGIS Windows Mobile Standard Workflows are generated from the CPT Calculator tab.

  • ArcGIS Mobile sample Standard Workflows include the ArcGIS Mobile client, the mobile synchronization service, and the mobile provisioning service.
  • Additional custom mobile workflows can be generated from the CPT Calculator tab based on the workflow software technology performance factors similar to the sample workflow recipe provided for the ArcGIS Mobile Standard Workflows.


Figure A-2.6 Some sample ArcGIS Mobile standard workflow performance targets are provided on the CPT Workflow tab.

Figure A-2.6 shows the ArcGIS Windows Mobile workflow patterns available on the CPT Workflow tab.

  • AGS ArcGIS Mobile synchronization service: Use for simple point or polygon edits that are synchronized with the server during edit operations. Workflow productivity should be adjusted to represent workflow edit loads.
  • AGS ArcGIS Mobile provisioning service: Use for simple local extent business layer downloads representing new job tasking. The basemap cache should be downloaded before going to the field. Workflow productivity should be adjusted to represent frequency of project data downloads.


ArcGIS Mobile standard workflow description

Figure A-2.7 The ArcGIS Mobile workflow description identifies the recipe used to generate performance targets for each project workflow.

Figure A-2.7 shows the ArcGIS Mobile workflow descriptions. Each of the ArcGIS Mobile Standard Workflows include a Calculator recipe provided as the Workflow Description (column AB).

  • Wireless synchronization is limited to 10% of a medium complexity vector display (business layers for a simple edit operation). The mobile synchronization service uses a SOAP 2D medium complexity 10% Dynamic (limited to exchanging updated features streamed to client over SOAP interchange) with 1366x768 display.
  • The provisioning service downloads 100% of the business layers for each new project for the work area of extent (basemap layers should be loaded on the device before going into the field). The mobile provisioning service downloads 100% of the dynamic 2D vector display business layers using a SOAP web service connection.

Workflow service times should be generated based on specific workflow properties, providing a reasonable performance target for capacity planning. Workflow service times for a variety of other custom mobile applications can be generated from the CPT Calculator tab, similar to the ArcGIS Mobile demonstration.

CPT Geoprocessing services

A variety of ArcGIS analysis (Geoprocessing), generating map or imagery cache tiles, or performing data replication services all can be represented by batch processing loads. Geoprocessing services are executed as single threaded batch processes, consuming available resources with transaction response time = service time (no random arrival queue time). Geoprocessing services are compute intensive, and with properly configured servers each geoprocessing instance will consume available processor core resources during peak system loads.

Geoprocessing services are represented in the Capacity Planning Tool by setting the project workflow minimum think time equal to zero. Each instance of a workflow profile with minimum think time set to zero will perform as a batch process.

CPT Geoprocessing standard workflows

Figure A-2.8 The CPT Workflow tab includes Citrix, SOC, and DBMS standard batch workflows.

Figure A-2.8 shows the CPT geoprocessing standard workflow selections. Standard workflow selections can be used for geoprocessing instances executed on a single platform tier.

  • AGD Citrix GeoBatch. Geoprocessing load supported by the Citrix platform tier.
  • AGS SOC GeoBatch. Geoprocessing load supported by the GIS Server (SOC) platform tier.
  • AGS DBMS GeoBatch. Geoprocessing load supported by the DBMS platform tier.


CPT Geoprocessing workflow performance

Figure A-2.9 AGS SOC GeoBatch geoprocessing workflow loads.

Figure A-2.9 shows the AGS SOC GeoBatch standard workflow processing loads for a single instance selection.

  • Workflow tab is selected as the Workflow Source (cell C30).
  • AGS SOC GeoBatch is the workflow selection(cell E30).
  • Single instance processing load (cell A6) consumes a processor core on the Web/SOC platform tier (25% utilization on 4 core server) shown in cell H10.


Any workflow pattern can be used to generate a batch process. For example, a standard Web services with min think time = 0 (cell D6) can be used to generate map caching or geodatabase replication loads across a multiple machine architecture.

Project Workflow assignment (Standard Workflows)

Figure A-2.10 Standard Workflows are included on the CPT Workflow tab for simple Project Workflow selection.

Figure A-2.10 shows how to move a selected Standard Workflow on the CPT Workflow tab to your Project Workflow section, and how to identify a unique Project Workflow nickname for use in your design.

Standard Workflows located on the CPT Workflow tab represent the most common ArcGIS deployment patterns. The following procedure can be used to select a Standard Workflow and insert copied cells (insert a new workflow row) in your Project Workflow section.

  • Select and Copy the row containing the standard workflow you would like to use.
  • Select Row just below where you want to insert the new workflow in your Project Workflow section.
  • Insert Copied Cells to include a copy of the Standard Workflow in your Project Workflows.
  • Select workflow name in column A and add nickname followed by an underscore (WebMap_) to the new Project Workflow.

Once you have added the new Standard Workflow to your Project Workflow section and, included a nickname to make the workflow name unique, you are ready to use the new workflow in your CPT Design.

CPT Capacity Planning videos

Chapter 2 Capacity Planning Video will introduce the ArcGIS platform software workflow patterns included in the CPT and show the Standard ArcGIS Workflows included on the CPT Workflow tab.

Capacity Planning Tool TABLE OF CONTENTS 41st Edition
1. System Design Process (CPT Demos) 41st Edition 2. GIS Software Technology (CPT Demos) 41st Edition 3. Software Performance (CPT Demos) 41st Edition
4. Server Software Performance (CPT Demos) 41st Edition 5. GIS Data Administration (CPT Demos) 41st Edition 6. Network Communications (CPT Demos) 41st Edition
7. Platform Performance (CPT Demos) 41st Edition 9a. GIS Product Architecture (CPT Calculator Demos) 41st Edition 9b. GIS Product Architecture (CPT Design Demos) 41st Edition
10. Performance Management (CPT Demos) 41st Edition 11a. City of Rome Year 1 (CPT Demos) 41st Edition 11b. City of Rome Year 2 (CPT Demos 41st Edition)

Page Footer
Specific license terms for this content
System Design Strategies 26th edition - An Esri ® Technical Reference Document • 2009 (final PDF release)