Capacity Planning Tool

From Wiki.GIS.com

Jump to:navigation, search
System Design Strategies (select here for table of contents)
1. System Design Process 2. GIS Software Technology 3. Software Performance 4. Server Software Performance
5. GIS Data Administration 6. Network Communications 7. GIS Product Architecture 8. Platform Performance
9. Information Security 10. Performance Management 11. System Implementation 12. City of Rome
A1. Capacity Planning Tool B1. Windows Memory Management Preface (Executive Summary) SDSwiki What's New


Fall 2014 Capacity Planning Tool 35th Edition
Capacity Planning Tool updates

This Capacity Planning Tool appendix shares CPT demonstrations used to identify system design requirements and model performance and scalability of proposed GIS operations.

The CPT demonstrations expand on the design concepts discussed in the primary System Design Strategies chapters, where hyperlinks to this appendix demonstrate how the CPT can be used to reinforce core system design concepts introduced in the primary documentation.

The CPT provides a framework for integrating business, data, applications, and technical architecture needs required to design, deploy, and manage successful enterprise GIS operations. This appendix can be used as a resource for learning how to use and apply the CPT in addressing your system architecture design needs.

This Chapter also includes a series of videos that demonstrate how the CPT can be used to collect business requirements, select the right software technology, identify the proper platform solution, and model Enterprise system performance and scalability.

Contents

System Design Process

Figure A-1.1 The Capacity Planning Tool is designed to automate the system architecture design performance analysis during the system design process.

The Capacity Planning Tool (CPT) simplifies business requirements data collection and automates system design analysis tasks associated with each phase of the development cycle. This section will introduce the CPT and show how the tools are used to complete a system architecture design.

The system design process starts with a business workflow loads analysis, identifying your GIS workflows and estimating the complexity of your business processes.


Workflow loads analysis

Figure A-1.2 Understanding your business needs is a prerequisite for completing your system design.
Figure A-1.2 shows the first steps in preparing for the design process. A clear understanding of your organization is critical in building successful GIS operations. Business planning starts with establishing an enterprise GIS vision, and building an implementation strategy that takes full advantage of your existing business architecture. Identifying the business workflows within your organization that can benefit from GIS information products is an essential ingredient for getting started on the right path to a successful system architecture design. Business needs (user requirements) establish the foundation for selecting a proper system design. Business requirements in the CPT are represented by project workflows.

The first step in completing a system architecture design is to select appropriate project workflows to represent your business requirements. Your selected project workflows identify the processing loads that must be supported by your selected hardware solution to satisfy your business needs.

CPT Calculator tab: Custom workflow loads analysis

Figure A-1.3 The CPT Calculator is a simple tool developed for use during business workflow loads analysis and software technology selection. The Calculator tab was designed for use in defining custom workflow performance targets. A selection recipe is used to generate appropriate custom workflow service times from a baseline set of performance benchmarks.
The Calculator shown in Figure A-1.3 provides a group of drop-down lists for workflow software technology selection (software, map document, density, percent data cache, complexity, map resolution, output format). A proper software technology selection will generate appropriate GIS workflow performance targets (service times) for use in your system architecture design.

The CPT Calculator can also be used to complete the system architecture design for a selected workflow. There is an option (cell C30) available to select your workflow source (Calculator or Workflow tab).

Warning: Capacity Planning Tool color scheme: Inputs to the Capacity Planning Tool are provided in the white cells (most inputs are drop-down lists). Formulas for the analysis are included in the colored cells. You should not change the colored formula cells.
Note: CPT Calculator tab is discussed in more detail in the CPT section on Software performance.


CPT Workflow tab: Workflow loads definition

Figure A-1.4 Workflow tab is used to define project workflows. It includes standard workflows and links for custom, test, and composite workflow performance targets.
Figure A-1.4 shows the CPT Workflow tab. A list of Standard Workflows is maintained in the Workflow tab for simple selection of the most common workflow performance targets. Custom workflows configured on the CPT Calculator tab include an output to the CPT Workflow tab (Calculator Workflow section).

The Project Workflows section is established at the top of the workflow list by including a copy of standard or custom workflows in your project workflow list – selection of your project workflows completes your workflow loads analysis. Once your workflow loads analysis is complete, your selected workflow performance targets will be available at the top of the workflow selection list for use in your system architecture design.

The composite workflow analysis section located at the bottom of the Workflow tab is used to calculate average service times for a use-case that combines two or more component workflows. A demonstration of a composite workflow loads analysis is included in the Greek Citizen Declaration case study at the end of Chapter 4.

Note: The CPT Workflow tab is discussed in more detail in the CPT section on GIS software technology.


System architecture design

Figure A-1.5 System Architecture Design process provides a logical step by step methodology for using the CPT to complete your System Architecture Design.
Once you have identified your project workflows, you are ready to complete your system design. The CPT follows a standard system architecture design process as shown in Figure A-1.5. Each cycle of the system architecture design process includes the following steps:

The system design process includes the user requirements analysis, network suitability assessment, platform architecture selection, software configuration (installation), and the Enterprise design solution. The CPT was designed to complete the analysis. Once the CPT is properly configured and business requirements are defined, the CPT will complete the system architecture design analysis and display the platform solution.

CPT Design tab: User requirements analysis

Figure A-1.6 User requirements analysis. User requirements are identified by configuring the workflow rows and peak loads located at the top of the CPT design tab.
User requirements analysis—CPT Requirements analysis section is configured to represent the site locations, user workflows, peak loads, and network bandwidth for the enterprise design solution.


Figure A-1.7 The CPT Design tab includes a Requirements Analysis module designed for use in configuring your user requirements for CPT design analysis.
Once you identify your business workflows, you are ready to complete a user system loads analysis. The CPT Design tab includes a Requirements Analysis module where you can identify user locations and peak throughput loads.

Figure A-1.7 shows the CPT Design tab Requirements Analysis module. The gray rows represent the data center network connections (LAN, WAN, Internet) while the green rows represent remote site network connections. Workflows for WAN users are located under the data center LAN network. Remote user workflows are located below each remote site network, based on user work locations.

Peak concurrent users and workflow productivity establish system throughput loads that drive the system architecture design. These loads include network traffic that must travel between the user display location and the central data center. Location of the workflow users and how their locations are connected with the central data center can directly impact software technology selection.

Warning: Capacity Planning Tool color scheme: Inputs to the Capacity Planning Tool are provided in the white cells (most inputs are drop-down lists). Formulas for the analysis are included in the colored cells. You should not change the formula cells.
Note: An example of an Enterprise user requirements analysis was provided in Chapter 12: City of Rome.


CPT Design tab: Network suitability analysis

Figure A-1.8 Network suitability analysis. The CPT completes the network suitability analysis once the user requirements configuration is complete.
Network suitability analysis—CPT Design completes the network suitability analysis and identifies any communication bottlenecks. Network bandwidth upgrades are identified and upgrades are entered to resolve identified network contention.


Figure A-1.9 The CPT Design: Requirements Analysis module completes a network suitability analysis based on user location, peak system loads, and available network bandwidth.
Once you configure the CPT Design tab to reflect your user requirements and identify the network connections, the CPT completes a network suitability analysis. The CPT analysis evaluates network bandwidth and latency to ensure adequate capacity to accommodate peak traffic flow loads. You can then increase network bandwidth as required to accommodate peak traffic loads. Figure A-1.9 shows the business workflow, peak loads, and network bandwidth inputs needed to complete the network suitability analysis.


Figure A-1.10 Results of the network suitability analysis are used to identify appropriate network bandwidth upgrades. Once the network upgrade bandwidths are entered, the CPT Design tab shows a valid enterprise-level workflow solution.
Once the business requirements analysis is complete (user locations, peak workflow loads) available bandwidth for each network must be entered in column H. The CPT completes the network suitability analysis, and identifies associated design conflicts (user productivity and network traffic). Analysis results provide information needed to complete the network design. Figure A-1.10 shows the network suitability analysis results once the network upgrades are made.

Once bandwidth upgrades are made, the traffic flow and productivity conflicts are removed.

Warning: Capacity Planning Tool color scheme: Inputs to the Capacity Planning Tool are provided in the white cells (most inputs are drop-down lists). Formulas for the analysis are included in the colored cells. You should not change the formula cells.
Note: Network Suitability Analysis was discussed in Lesson 6: Network communications.


CPT Design tab: Platform architecture selection

Figure A-1.11 Platform architecture selection. The data center architecture selection is configured for each platform tier located on the bottom rows of the CPT Design tab.
Platform architecture selection—CPT Design Platform tier is configured to represent the data center platform architecture structure. Identify platform tier nicknames, select platforms, and identify platform rollover settings.


Figure A-1.12 The CPT Design: Platform selection module allows you the ability to select your desired platform configuration.
Figure A-1.12 shows the CPT Design Platform Configuration module. The platform selection (column B) is normally configured first, and platform nicknames followed by a colon (:) can be identified for each tier just above the platform selection in column B. You can also set a rollover setting in column H, telling the Capacity Planning Tool when to add new platforms.

Platform selection is a critical decision in any design process. The selected platform directly contributes to user display performance, platform capacity, and software licensing cost. A faster processor core (column F) improves user performance and reduces license cost. Higher capacity servers (column G) reduce the total number of server machines required to satisfy business requirements.

Warning: Platform selection directly impacts overall system cost.

Once the platform names are set, you can complete the system install in the Software Configuration section.

Note: CPT Design: Platform selection is discussed in more detail in Chapter 8: Platform performance.


CPT Design tab: Software configuration

Figure A-1.13 Software configuration. The workflow software is installed on the appropriate platform tier to complete the system configuration.
Software configuration—CPT Design Software Configuration module is used to assign workflow software to supporting platform tier (software install) and make workflow data source selection.


Figure A-1.13 Once you have identified your selected platform configuration, the CPT Design: Software configuration module is used to complete the software installation.
Figure A-1.13 shows the CPT Design Software Configuration module. Once you establish your platform architecture, you are ready to install the workflow software. Software install is defined in the Software Configuration section (columns J through R) for each user workflow.

Workflow software components you must install are identified by colored blocks in the software configuration section.

Note: CPT Design software configuration patterns are discussed in more detail in the CPT product architecture section.


CPT Design tab: Enterprise system design

Figure A-1.15 Enterprise design solution. System architecture design analysis performed by the CPT completes the design.
Enterprise design solution—Once configured, the CPT Design tab completes the system architecture design analysis and provides the platform solution.


Figure A-1.16 The CPT Design tab completes an enterprise level system architecture design analysis once you have entered your business workflow needs, available network bandwidth connectivity, and selected platform configuration.
Figure A-1.16 shows the resulting Enterprise system design. Once you make your platform selections and install workflow software components (software configuration), the CPT will complete the platform sizing and show the required server configuration (number of platforms and peak utilization levels for each platform tier).

The Design tab provides a snapshot view of your user requirements and associated platform solution as a single integrated information product.

Note: Chapter 12 provides a case study for the City of Rome, demonstrating how to use the CPT to complete an enterprise system architecture design.


CPT Hardware tab: Platform performance

Figure A-1.17 The CPT Hardware tab is used to list SPEC performance benchmark values for use in completing the system architecture design.
Platform performance metrics are pulled from the Hardware tab, shown in Figure A-1.17. The Hardware tab provides a list of available platform configurations each with the following information:


Benchmark results are collected from the SPEC benchmark site for each vendor platform configuration. This platform performance information is used by the CPT to complete the system architecture design analysis.

Note: CPT hardware tab and performance benchmarks is discussed in more detail in Lesson 8: Platform performance.


CPT Test tab: Performance validation

Figure A-1.18 Performance validation is critical to ensure compliance with system design performance targets.
Figure A-1.18 identifies opportunities for measure performance compliance when deploying your GIS operations.

Measuring performance during the system build and deployment reduces implementation risk. System design is only the beginning of the process; then you need to build a system that performs within the system architecture design performance targets. If measured performance loads exceed planned budgets, adjustments can be made to workflow complexity during the build process to deliver services within initial performance targets.

The CPT Test tab was designed to help with the validation process, and includes several tools that can be used to translate performance measurements to equivalent workflow service times.

Figure A-1.19 The CPT Test tab provides tools for use in translating performance measurements to workflow performance targets that can be used to generate those measured loads.
Figure A-1.19 shows the measured performance analysis tools available on the CPT Test tab.

There are four Test tools that you can use during system deployment.

Best practice:
  • Evaluate performance compliance during initial prototype testing.
  • Validate system performance goals are met during initial production deployment.
  • Establish periodic performance validation milestones throughout production.
Note:Test tab is discussed in more detail in the CPT section on Performance validation


Platform Capacity Calculator (Hardware tab)

Figure A-1.20 The CPT Hardware: Platform Capacity Calculator is a simple tool you can use to select a hardware configuration. It will then calculate light and medium complexity throughput capacity estimates for the selected workflow configuration.
Figure A-1.18 shows the CPT Platform Capacity Calculator. The Platform Capacity Calculator is located at the bottom of the CPT Hardware tab.

The Platform Capacity Calculator provides a peak throughput range for a list of selected Workflows, showing medium complexity output in blue and light complexity output in red. This simple tool answers many of the most important questions customers have when purchasing Esri software (What throughput can I expect from the selected hardware?).

The Platform Capacity Calculator is simple to use.

Workflow candidates on the left of the chart can be modified to represent any workflow listed on the CPT workflow tab, including your project workflows. Simply slide the graphic to the side and the workflow selection cells are available directly behind the chart. The total number of workflow candidates can be increased or decreased to by expanding or contracting the workflow rows to satisfy your reporting needs.

CPT Capacity Planning videos

Chapter 1 Capacity Planning Video introduces the Capacity Planning Tool and provides an overview of the System Architecture Design process. The next section shows CPT software technology patterns discussed in Chapter 2: GIS Software Technology.

GIS Software Technology

Figure A-2.1 ArcGIS shares a global platform for working with maps and geographic information.
ArcGIS share 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:

- Workstation
- Windows terminal server
- Web mapping
- Imagery
- Windows mobile

CPT desktop workflows

ArcGIS for 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 for Desktop software technology selections.

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

Note: Workflow complexity is 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.

Note: The Software technology selection section in the software performance chapter provides more information on selecting appropriate workflow performance targets.


ArcGIS for Desktop Standard Workflows

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

Figure A-2.3 shows the ArcGIS for 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 for Desktop workflow patterns are pre-generated from the Calculator tab and included on the Workflow tab as Standard Workflows.

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

CPT server workflows

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

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

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

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

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.


ArcGIS for Server standard workflows

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

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

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

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 light and medium 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.

CPT Mobile Workflows

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

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


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

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


ArcGIS for Windows Mobile standard workflow description

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

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

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 for Windows Mobile demonstration.

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.

Software Performance (CPT Calculator)

Figure A-3.1 The CPT Calculator can be used to generate custom workflow service times for use in your system design.

This section shares lessons learned about selecting and building effective GIS design solutions that satisfy operational performance and scalability needs. Software technology allows us to model our work processes, and provide these models to computers to optimize user workflow performance. The complexity of these models, the functions selected to generate our display, the complexity of the data source, and how application functions are orchestrated to analyze and present information processing needs all have a significant impact on computer system workload and subsequent performance and scalability.

Workflow description is retained in a workflow recipe. Performance factors used to generate the workflow recipe include the following:

Proper workflow selection establishes the foundation for a successful system architecture design.

Software technology selection

Figure A-3.2 CPT Calculator software selection establishes the workflow baseline. The drop-down list shows the software technology profile selections available in the CTP Calculator.
The GIS software technology patterns were introduced in Chapter 2. The CPT Calculator can generate workflow processing loads from a variety of software technology patterns. Figure A-3.2 shows the CPT Calculator Software dropdown list located in cell E3 providing a list of the available software technology selections. Your Software technology selection identifies the baseline used for generating the selected workflow processing loads.

Map Document/Imagery selection

The CPT Calculator cell title will change based on the software technology selection. The Map document (MapDoc) dropdown selection is provided for GIS workflows, and the Imagery data management (Imagery) dropdown selection is provided for the ArcGIS for Server Imagery workflows.

ArcGIS map document (MapDoc) selection

Figure A-3.3 CPT Calculator MapDoc selection. This is a dropdown list that identifies which rendering engine will be used by the map service.
Figure A-3.3 shows the CPT Calculator MapDoc selection in cell G3. The selection options are MXD or MSD. The selection choice is included in the Workflow recipe.


ArcGIS imagery selection

Figure A-3.4 CPT Calculator imagery selection. The imagery selection identifies which type of dataset is used for managing access to imagery data.
Figure A-3.4 shows the CPT Calculator Imagery selection in cell G3. The selection options are MosaicDS or RasterDS. The selection choice is included in the Workflow recipe.

Mosaic dataset host is selected in cell A11 (FGDB or DBMS). When selecting an Imagery workflow, cell J6 will provide a list of available Imagery data formats.

ArcGIS density/portal selection

Figure A-3.5 CPT Calculator Density selection. The density/portal selection modifies workflow traffic and rendering time processing loads. Portal configurations modify registered services to include Web portal processing loads
Figure A-3.5 shows the CPT Calculator Density/Portal selection in cell H3. The selection choice is included in the Workflow recipe (V for Vector Only and R for Raster Image, include Portal when services are registered with a Portal Web server).

Portal for ArcGIS registered workflows

Portal for ArcGIS provides a collaborative content management systems that organizations can deploy in their own infrastructure (on premises or in a private cloud). Portal establishes a common reference location for self-service ArcGIS services management and collaboration throughout the organization.

Portal selections (VPortal and RPortal) identify workflow density for hosted ArcGIS for Server workflows registered with Portal, and these workflows include increased service time on the Web service component for Portal content management processing along with the GIS Server processing loads.

A majority of Portal operations include creating Web Maps and/or adding services to the site, actions which establish registered services with the Portal for ArcGIS site. Portal Web Maps that include services from external Internet sources should use the Portal workflow (no internal hosted service loads). Internal registered services should use portal in the density/portal selection for creating the portal loads.

ArcGIS percent data cache (%DataCache) selection

Figure A-3.6 CPT Calculator MapCache selection. The map cache setting identifies how many layers will be pre-processed into a tiled map cache.
Figure A-3.6 shows the CPT Calculator %DataCache selection in cell I3. The percent dynamic is calculated (1-%DataCache) and the %Dyn percentage is included in the Workflow recipe.


Display complexity selection

Figure A-3.7 Display complexity is used to establish workflow performance targets; selection identifies the display processing load relative to a medium complexity baseline workflow.
Figure A-3.7 shows the CPT Calculator workflow complexity selection in cell E6. Map complexity setting is identified in the workflow recipe. Workflow service time adjustments are applied to the application and database service times.

Workflow complexity directly impacts display performance and system cost. CPT Calculator was used to generate results for an ArcGIS for Server REST V mapping service supporting 100,000 TPH with Xeon E3-1270v3 4 core (2 chip) 3500 MHz servers:


Resolution selection

Figure A-3.8 Calculator resolution selection identifies the map output display size. More traffic is required when publishing larger map resolution.
Figure A-3.8 shows the CPT Calculator resolution selection in cell F6. Selection is included in the workflow recipe in hundreds of pixels. Select a resolution that best matches the average map size of your published service. The map resolution rendered by the published map service is often determined by the size of the client map display.


Output selection

Figure A-3.9 Several output service formats are available for map publishing. Select the format that applies to your published service. Calculator will use the output look-up table to adjust traffic and loads based on your selection.
Figure A-3.9 shows the CPT Calculator output selection in cell G6. Output selection makes a difference in both traffic and processing loads. Select an output that matches your published service.


Vector storage format selection

Figure A-3.9 Several vector data source formats are available for your selection. Calculator will use a look-up table to adjust output traffic and loads based on your data format selection.
Figure A-3.10 shows the CPT Calculator data source selection in cell J6. GIS workflow application service time and traffic adjustments are made as shown in the data source adjustment table based on the data source selection.

Selection provides a dropdown list of standard GIS vector data sources.


Imagery storage format selection

Figure A-3.11 Several imagery data source formats are available for your selection. Calculator will use a look-up table to adjust output traffic and loads based on your data format selection.
Figure A-3.11 shows the CPT Calculator imagery data source selections in cell J6. GIS workflow application service time and traffic adjustments are made as shown in the data source adjustment table based on the data source selection.
Note: Additional information on imagery management strategies is provided in Lesson 4: GIS data administration.


Standard workflow selections

Figure A-3.12 CPT Calculator standard workflow selection with peak loads of 100,000 TPH will require two Xeon Xeon E3-1280V2 4 core (1 chip) 3600 MHz GIS server platforms.
Standard Workflows included on the CPT Workflow tab were introduced in Chapter 2. Figure A-3.12 shows how you can select project workflows or standard workflows at the bottom of the Calculator input display.

ArcGIS 10.2 for Server Standard workflow selections

Best Practice: Optimum complexity settings generate reasonable system design performance targets.
Warning: Workflow complexity established too high during design will generate inflated hardware and licensing cost estimates.
Workflow complexity established too low during design can increase deployment risk.

Medium complexity workflows will satisfy most standard web mapping deployment needs.

Custom workflow processing loads

Figure A-3.13 Custom workflow performance loads are generated from baseline workflows. Calculations begin with the selected baseline service times at the bottom row and work to the adjusted workflow service times at the top. Selected software performance factors are applied to generate custom baseline service times.
Figure A-3.13 shows the calculations made by the CPT Calculator in generating adjusted custom workflow loads. CPT Calculator workflows are generated from performance benchmark baselines.

Starting point

First adjustment

Additional selection impact on workflow loads


Figure A-3.14 Custom workflow service times created on the Calculator tab are copied to CPT Workflow tab. Workflow service times can then be copied and included in Project Workflows
Figure A-3.14 shows where the CPT Calculator workflow service times show up on the Workflow tab. Calculator workflows provide a source for both standard and custom workflow performance targets.

Calculator workflows are copied to the CPT Workflow tab to include in project workflows.

Best Practice: Software technology baseline service time, traffic loads, and relative performance adjustments are derived from test benchmarks.


CPT Capacity Planning videos

The next section will take a closer look at ArcGIS Server software performance.

Server Software Performance

CPT Design batch process instance configuration

Figure A-4.1 Batch process loads

The brown line in Figure A-4.1 shows the maximum host platform throughput in displays per minute (DPM) for a series of ArcGIS Server batch process service configuration instance settings. The bars show host platform service time (colored tier) and service wait times (wait times are due to shared use of the available core processor). The host platform has 4 core; the four core processors are shared resources used to execute the deployed service instances.


Figure A-4.2 CPT Design tab used to demonstrate the optimum number of batch process service instances.

Figure A-4.2 shows the CPT Design tab configured for a batch process service instance demonstration. The purpose of the demonstration is to show the optimum service instance configuration for a batch process.

CPT Design tab configuration

Warning: The RESET ADJUST function in Cell AF2 must be used to calculate batch process productivity.

With the design tab configured for the batch process instance demonstration, the number of instances can be entered in the services column to represent each of the bars in Figure A-4.1. Results should follow the brown line on the chart as the instance configuration is increased.

CPT Design map service instance configuration

Minimum and maximum service instances are identified when publishing a map service. It is important to identify the proper instance configuration for each map service deployment. Proper service instance configurations depend on the expected peak service demands and the server machine core processor configuration.

Figure A-4.3 Web mapping service instance load profile.

The blue line in Figure A-4.3 shows the peak host platform throughput in displays per minute (DPM) for a series of ArcGIS Server service configuration instance settings responding to random Web service requests. The bars show GIS Server machine service time (colored tier) and service queue times (processing queue times result from random arrival of service requests). The server machine has 4-core; the four core processors are shared resources used to execute the deployed service instances.

Figure A-4.4 CPT Design tab used to demonstrate the optimum number of Map service instances.

Figure A-4.4 shows the CPT Design tab configured for a Web mapping service instance demonstration. The purpose of the demonstration is to show the optimum service instance configuration for a defined Web mapping service.

CPT Design tab configuration

Warning: The RESET ADJUST function in Cell AF2 must be used to calculate map instance maximum productivity.

With the design tab configured for the Web mapping service instance demonstration, the number of instances can be entered in the services column to represent each of the bars in Figure A-4.3. Results should follow the brown line on the chart as the instance configuration is increased.

Selecting the right technology: A case study

Selecting the right software technology can make a big difference in performance and scalability, and cost of the production system. The following case study shares an experience with a real customer implementation which clearly represents the value of selecting the right software technology.

User requirements for web mapping solution

Figure A-4.5 This network diagram shows the central National Data Center and sample small and large regional centers used in completing the design.

Figure A-4.5 shows an overview of the national architecture. The initial system design was developed using an earlier ArcGIS for Server web application development framework (ADF) map editor, hosting a centralized ArcGIS for Server dynamic web application with browser clients located at 60 regional national sites. Following contract award, the customer reviewed available technology options to finalize the system design.

Peak web service use requirements


Web mapping services architecture patterns.

Figure A-4.6 Four ArcGIS for Server web technology patterns were considered. They included an early Map Editor ADF application, two Adobe Flex applications, and one Windows Mobile application.

Figure A-4.6 shows the ArcGIS for Server architecture patterns that were considered for the Greek citizen declaration solution.

Initial hardware proposal

The following workflow was used to generate system loads for the initial hardware proposal.

CPT Workflow: AGS10 ADF MXD R 100%Dyn Lite 10x7 JPEG
System implementation design review (after grant approval)

After some time, the European Union approved the Greek Citizen Declaration grant based on the initial hardware proposal. The Greek cadastral team traveled to Esri to review available technology options for final implementation.

The following web mapping services architecture patterns were reviewed to identify optimum deployment scenario.

CPT workflow: AGS10 ADF MXD R 100%Dyn Lite 10x7 JPEG
CPT workflow: RESTdyn_Composite Workflow from the following composite recipe:
  • Basemap_AGS102 REST MSD R 90%Dyn Lite 10x7 JPEG
  • busLayer_AGS102 REST MSD R 10%Dyn Lite 10x7 Feature
  • 100 percent dynamic
CPT Workflow: AGS102 REST MSD V 10%Dyn Lite 10x7 Feature +$$
CPT Workflow: AGS102 SOAP MSD V 5%Dyn Lite 10x7 Feature
Best Practice: Significant technology improvements have become available since the initial proposal. It is always good to update the final solution architecture based on current technology before final implementation.

Web ADF application with central dynamic SDE data layers

Figure A-4.7 CPT Calculator design shows platform solution when supporting business needs using 100 percent dynamic web ADF map editor server technology

Figure A-4.7 shows the CPT analysis for the dynamic Web ADF application solution. Standard E3-1270v3 4-core (1 chip) 3500 MHz servers were used for this assessment. These are high performance 2014 server platforms.

CPT Workflow: AGS10 ADF MXD R 100%Dyn Lite 10x7 JPEG

Peak system requirements:

Hardware solution:

Peak network traffic estimates

Best Practice: Rich internet application clients provide the most optimum user performance and system scalability. Web ADF Map Viewer and Map Editor components were depreciated following the ArcGIS 10 release - RIA clients are a much simpler programming environment and deliver significant performance and scalability improvements]


Web Flex application with central dynamic SDE data layers

Figure A-4.8 CPT Calculator composite workflow analysis tool is used to calculate composite service times for display mash-up of dynamic business layer feature service with dynamic basemap layer map service.

The Web Flex application will use a REST Feature service for the business layer mashup with a dynamic REST Map service for the basemap layer. Figure A-4.8 shows the CPT composite workflow analysis to generate the REST dynamic workflow.

CPT workflow: RESTdyn_Composite Workflow from the following composite recipe:

  • Basemap_AGS102 REST MSD R 90%Dyn Lite 10x7 JPEG
  • busLayer_AGS102 REST MSD R 10%Dyn Lite 10x7 Feature
  • Both services are required for 100 percent of the dynamic map displays


Figure A-4.9 CPT Calculator design shows platform solution when supporting business needs using 100 percent dynamic Web FLEX Map Editor server technology.

Figure A-4.9 shows the CPT Calculator analysis for the 100 percent dynamic Web Flex application. Standard E3-1270v3 4-core (1 chip) 3500 MHz servers were used for this assessment.

CPT Workflow: RESTDyn_Composite Workflow Analysis

Peak system requirements:

Hardware solution:

Peak network traffic estimates


Web FLEX application with point feature layer + central map cache

ArcGIS Server provides a data cache option where reference map layers could be pre-processed and stored in a map cache pyramid file data source. Pre-processing the reference layers would significantly reduce server processing loads during production operations. A single point declaration layer contained all features that would be edited and exchanged during the citizen declaration period; all remaining reference layers could be cached. Changes would be displayed at all remote site locations with each client display refresh.

Figure A-4.10 CPT Calculator design shows platform solution when supporting business needs using 10 percent dynamic web FLEX map editor server technology with cached basemap service.

Figure A-4.10 shows the CPT Calculator analysis for the Web Flex application with a cached basemap. Standard E3-1270v3 4-core (1 chip) 3500 MHz servers were used for this assessment.

CPT Workflow: AGS102 REST MSD V 10%Dyn Lite 10x7 Feature +$$

Peak system requirements:

Hardware solution:

Peak network traffic estimates


Web mobile application with edit feature synchronization + local map cache

The fourth design option was to use the ArcGIS Mobile application with a local reference cache data source. A demo of the ArcGIS Mobile client was provided on a Windows desktop platform to demonstrate feasibility of supporting the required editing functions with this client technology. The ArcGIS Mobile client technology operates very well on a standard Windows display environment and performed all the functions needed to support the citizen declaration requirements.

Figure A-4.11 ArcGIS 10.2 for Server SOAP mobile synchronization service with map cache basemap.

The ArcGIS Mobile standard workflow synchronization service was used to support the design analysis. This workflow was generated by the CPT Calculator using a SOAP MXD Light service with a feature output (display features streamed to the client application). A 95 percent data cache setting was used to represent traffic for point feature exchanges (only point changes would be exchanged between the client and server displays). Cached reference layers would be distributed to each regional site in advance, and access would be provided by a file share to the ArcGIS Mobile clients running on the local workstations. The ArcGIS Mobile client would synchronize point changes to the dynamic citizen declaration layer over the government WAN. The peak concurrent SOAP service load would be reduced to 600 concurrent users, representing 25 percent of the total client displays (point changes are made only during edit transactions).

Figure A-4.11 shows the CPT Calculator analysis for the Web Mobile application with a cached basemap. Standard E3-1270v3 4-core (1 chip) 3500 MHz servers were used for this assessment.

CPT Workflow: AGS102 SOAP MSD V 5%Dyn Lite 10x7 Feature

Peak system requirements:

Hardware solution:

Peak network traffic estimates:


Caching advantage summary

Figure A-4.12 Business analysis comparing the four software technology solutions.

It was very clear that the cached client application provided significant cost and performance benefits over the centralized Web application dynamic solution included in the initial proposal. Pre-processing of map reference layers as an optimized map cache pyramid can significantly improve display performance. Use of an intelligent desktop client that can access reference layers from a local map cache can minimize network traffic and improve display performance even more. Selecting the right technology can make a big difference in total system cost and user productivity. Figure A-4.12 highlights the advantage of selecting the right technical solution.

Best Practice: Selecting the right technology solution can make a big difference in price and user performance.

Business analysis identifies clear advantages in the ArcGIS for Mobile solution.

CPT Capacity Planning videos

Chapter 4 Capacity Planning Video will discuss best practices for configuring ArcGIS for Server for optimum performance and throughput.

GIS Data Administration

Figure A-5.1 Enterprise operations often include a combination of both GIS vector and imagery data resources supporting a variety of information services throughout the organization.

A variety of data management and deployment architecture strategies are available today to improve data access and dissemination throughout the rapidly expanding GIS user community. The volume of data you must sort through each day is growing exponentially. How you manage, organize, and control these data resources is critical to system performance and scalability.

This section will first show how to modify the CPT Platform Capacity Calculator workflow configuration to demonstrate the performance impact your data source format selections.

Finally, this section will demonstrate how to configure the CPT for an Imagery workflow.

Modifying the CPT Platform Capacity Calculator workflow configuration

The CPT Platform Capacity Calculator is a simple tool for evaluating selected platform capacity. The default tool, located at the bottom of the CPT Hardware tab, includes a variety of standard workflows that demonstrate platform capacity. For analysis and reporting purposes, you may want to change the default list of sample workflows and include those workflows you are evaluating in your own design environment. This section describes how you can change the Platform Capacity Calculator workflow samples to a custom set of workflows for demonstration purposes.

ArcGIS for Server mapping service data source performance comparison

The CPT provides six data source format selections for vector workflows. These selections include SDE_DBMS, Small File GDB, Large File GDB, Small ShapeFile, Medium Shapefile, and Large Shapefile. The CPT Platform Capacity Calculator default configuration includes a total of 5 workflows.

Figure A-5.2 Platform capacity output chart can be moved aside to expose the underlying workflow selection list. You can increase the number of workflows included in the Platform Capacity Calculator to provide sufficient bars to represent the available data source formats (six separate workflows).

Figure A-5.2 shows the location of the selected workflows displayed on the Platform Capacity Calculator. These workflows are located in column A directly behind the Platform Capacity chart. To access these workflows, use your mouse to select and drag the Platform Capacity chart to a location below the workflow selection list. The workflow selection list is a group of white cells in column A below the platform selection cell, normally located behind the Platform Capacity chart.

Adjusting the workflow display on the CPT Platform Calculator:

Warning: Make sure to select a workflow with Medium complexity.


Figure A-5.3 Select the desired data source for each workflow. In this case, a different data source for each workflow was selected.

Figure A-5.3 shows where you can select the data source format for each workflow. The data source for each workflow can be selected in column I (same row as the selected workflow). For this example, the AGS102 REST MSD R 100%Dyn Med 10x7 JPEG workflow was selected to demonstrate variation in performance between the available GIS vector data source selections. There are six different vector data source formats included in the CPT, so a total of six workflow rows were included in the demonstration. A separate data source was selected for each workflow in column I.

Once the workflows and data source selections are made, you can replace the Platform Capacity chart over the workflow selection list for the final analysis and display. When you select a platform configuration in column A, the Platform Capacity chart will show a peak platform throughput range for each of the selected workflows. The Platform Capacity chart shows 80 percent throughput estimates for both medium and light complexity workflow configurations.


Figure A-5.4 The Platform Capacity Calculator shows peak throughput values for medium and light complexity web map services deployed on a Xeon E5-2637v2 4-core (1 chip) 3500 MHz server.

Figure A-5.4 shows the modified custom Platform Capacity Calculator results. Selected platform configuration is the Xeon E5-2637v2 4-core (1 chip) 3500 MHz server. AGS102 REST MSD V 100%Dyn Med 10x7 PNG24 peak throughput varies from 20,600 TPH to 156,600 TPH depending on the display complexity and the selected data source.

Review final display.


ArcGIS for Server Imagery service data source performance comparison

The CPT provides seven file based data source format selections for Imagery workflows. These selections include TIFF uncompressed, TIFFLZW compression, TIFFJPG compression, JPG2000, MRSID, ECW, and IMG ERDAS. The CPT Platform Capacity Calculator workflow configuration can be adjusted to compare selected platform throughput capacity for the seven Imagery workflows.

Figure A-5.5 The Platform Capacity Calculator shows peak throughput values for medium and light complexity Imagery services deployed on a Xeon E5-2637v2 4-core (1 chip) 3500 MHz server.

Figure A-5.5 provides a view of the CPT Platform Capacity Calculator configured to show performance of the seven (7) available Imagery data source formats. The AGS102 Imagery MosaicDS R 100%Dyn recipe is used to represent the imagery workflow. The platform selection is the Xeon E5-2637v2 4-core (1 chip) 3500 MHz server configuration. The platform capacity output ranges from 16,700 TPH to 190,600 TPH based on selected data source and medium to light workflow complexity.

Procedure for adjusting the custom workflow display on the CPT Platform Capacity Calculator.

Warning: Make sure to select a workflow with Medium complexity.

Review the final display.


Selecting an imagery workflow on the CPT Calculator tab

Figure A-5.6 Select the CPT Calculator imagery workflow. Imagery workflows have unique Imagery, Density, and Platform Architecture selections.

Figure A-5.6 shows how to select an Imagery software pattern on the CPT Calculator tab.

Tip: Cells with unique selections will show in red.
Warning: New selections must be made in all red cells to configure a valid workflow.


Figure A-5.7 The imagery selection is either MosaicDS or RasterDS. Select MosaicDS for on-the-fly imagery processing.

Figure A-5.7 shows the Imagery dataset manager selection. Select the imagery dataset manager (MosaicDS or RasterDS) that will be used for workflow imagery data access.


Figure A-5.8 The Calculator will identify the Density/Portal setting in red if Raster is not selected.

Figure A-5.8 shows the Density/Portal selection. For all imagery workflows the Density selection must be Raster.

Workflows published on Server and registered through a Portal will use the VPortal or RPortal setting. the Portal selections increase the Web load to accommodate Portal services associated with the registered workflows.

Portal workflow software selection will be used to identify Portal data sharing and collaboration services for user workflows that do not consume registered services.


Figure A-5.9 MosaicDS metadata server is located in a geodatabase, either in a DBMS or a file geodatabase (FGDB).

Figure A-5.9 shows where to identify the mosaic dataset location. Select the location of the mosaic dataset (DBMS or FGDB).


Figure A-5.10 Selecting CPT Calculator imagery data format.

Figure A-5.10 shows the imagery data source format selection. The list of available imagery data formats are provided as a dropdown menu when you select an imagery workflow. Select the data source format planned for the imagery workflow.

Warning: The imagery data format can have a significant impact on performance.

Once the imagery workflow configuration is complete, the calculator completes the workflow sizing analysis and shows the resulting platform solution. You can then include the configured imagery workflow in your project workflows on the CPT Workflow tab for access when completing your design.

Selecting an imagery workflow on the CPT Design tab

Figure A-5.11 The Design tab provides a separate data list for imagery workflows. A red error will show in column H if the wrong data source type is identified.

Figure A-5.11 shows the CPT Design tab, highlighting the data source selection for an imagery workflow.

Warning: Be sure to select a data source format for each imagery workflow. New selections must be made in all red cells to configure a valid workflow.

The SDE selection in the CPT Design Software Configuration Module identifies the location for each workflow mosaic dataset. Proper selections are either the DBMS platform or a file geodatabase (FGDB).


Figure A-5.12 CPT Design solution for an imagery workflow selection.

Once you have configured the imagery workflow, you can view the design solution in Figure A-5.12. In this configuration, the GIS server platform is an E5-1280v2 4 core (2 chip) 3600 MHz server configuration hosting the AGS102 Imagery MosaicDS R 100%Dyn Med 10x7 JPEG workflow accessing a TIFF imagery data source. System loads are 100,000 TPH. The GIS Server is supporting these loads at a server utilization of 67 percent. Peak throughput loads for this workflow deployed on this server configuration is 149,000 TPH.

CPT Capacity Planning videos

Chapter 5 Capacity Planning Video will show how to reconfigure the CPT Platform Capacity Calculator to evaluate selected workflow performance.

Network Communications

Figure A-6.1 Enterprise network architecture

Network communications provide the required connectivity for distributed GIS operations. Network capacity, in many cases, can limit the software technology solutions that perform well within your organization. System architecture design must identify and address network communication constraints and provide the right technical solution for a successful GIS implementation.

This section will use the CPT to demonstrate network latency, Network configuration, and provide an overview of the network performance parameters identified on the CPT Workflow tab.

  • Network latency performance delays on the Calculator tab.
  • Network latency performance delays on the Design tab.
  • Configuring network architecture on the Calculator tab.
  • Configuring network architecture on the Design tab.
  • Network performance factors on the Workflow tab.

CPT network latency performance delays

Network chatter is included in each workflow on the CPT Workflow tab. Network latency is defined on the remote site network segments for each user workflow. The CPT will multiply network latency by workflow chatter to account for latency delays in calculating display response time.

CPT Calculator tab

Figure A-6.2 Latency is addressed for each remote location in the CPT Calculator in cells E13 and E14.

Figure A-6.2 shows how network latency is addressed in the CPT Calculator tab.

CPT Calculator rows 12, 13, and 14 address network communication traffic.

-LAN display performance is limited by client connection(client NIC bandwidth).
-Remote bandwidth analysis assumes the data center is not the bottleneck (set remote site bandwidth). The CPT Design tab must be used to complete a proper Data Center bandwidth suitability analysis.


CPT Design tab

Figure A-6.3 Latency is addressed for each remote site network in the CPT Design column S.

Figure A-6.3 shows how network latency is addressed in the CPT Design tab.

Network analysis is completed in the CPT Design Requirements Analysis section.


CPT Calculator network suitability analysis

Figure A-6.4 A single workflow network suitability analysis can be completed using the CPT Calculator.

Figure A-6.4 shows how the CPT Calculator tab can be used to complete a workflow network suitability analysis.

Best practice: CPT Calculator is a useful tool for evaluating single workflow network traffic contributions and the impact of available network capacity on remote site user productivity.
Warning:The CPT Calculator is limited to addressing a single workflow environment. Additional network traffic from other business operations will need to be included to complete the analysis.


CPT Design user requirements workflow loads analysis

Figure A-6.5 CPT Design user requirements module configuration establishes a foundation for completing the network suitability analysis.

Figure A-6.5 shows an overview of how the CPT Design tab can be configured to complete an enterprise network performance analysis.

The CPT Design shows the user workflow location relative to the data center and remote site network infrastructure.

Best practice: GIS user workflow loads analysis should be completed before establishing the final system architecture design.

The CPT Design requirements analysis module layout makes it possible to represent workflow display traffic flow across the appropriate service provider network connections.

Best practice: System design configuration begins with results from a user workflow loads analysis.


Figure A-6.6 Results of a user workflow loads analysis establishes requirements for the system architecture design.

Figure A-6.6 shows a sample of the results of a workflow loads analysis (Business Requirements Summary):


Figure A-6.7 CPT Design configured to represent the user workflow loads analysis.

Figure A-6.7 shows how to configure these same user requirements in the CPT Design

Best practice: Configuring the user requirements analysis module establishes a foundation for completing the CPT Design tab network suitability analysis.


CPT Design network suitability analysis

Initial user requirements loads analysis

Figure A-6.8 Network Suitability Analysis is completed by the CPT Design tab as you configure user locations, input peak workflow loads, and identify network bandwidth.

Figure A-6.8 shows an initial CPT Design tab requirements analysis configuration. The CPT Design tab will identify network bottlenecks as you complete configuration and inputs to the user requirements analysis.

Best practice: Increase network bandwidth to roughly twice expected peak traffic flows.


RESET ADJUST function

Figure A-6.9 Demonstrate impacts on user productivity due to network bandwidth constraints by using the RESET ADJUST tool on the CPT Design tab.
Figure A-6.9 shows the CPT Design once productivity was adjusted using the RESET ADJUST function. You can use the RESET ADJUST function to identify expected user productivity with existing bandwidth.

Under the Excel Options > Formulas section, make sure that the 'Enable iterative calculation' option is selected.

Warning: CPT will show a Circular Reference Warning if the enable iterative calculation option is not selected. You will need to reset the enable iterative calculation settings shown above for the CPT to work properly.
Best practice: Start with a Blink setting of 10 in cell AG2.
Note: ADJUST function uses excel iterations to identify productivity for batch processing workflows. As computed think time approaches zero, queue time increases to infinity (discontinuity) and processing loads exceed 100 percent capacity (not a valid solution). The BLINK setting determines the size of the productivity adjustments between each excel iteration. If the BLINK is too small, it can take thousands of iterations to converge on the correct productivity solution. If the BLINK setting is too large, the calculation will step across the discontinuity and the calculation must cycle below 100 percent capacity and try again. During high capacity loads, the BLINK setting should be reduced until the calculations can converge on the correct solution. Once the valid solution is reached, the throughput input cells will turn green.

The RESET ADJUST function resolves network bottlenecks.


Excel circular reference warning
Figure A-6.10 Excel will show a Circular Reference Warning when the iteration calculation option is not enabled.
The CPT analysis functions include iterative calculation options. Enable iterative calculations must be selected in the Excel Formulas Calculation options. Maximum iterations should be set at 500 and Maximum Change setting should be 0.001 for best CPT calculation performance. Figure A-6.10 shows the Excel Circular Reference Warning popup.


Workflow performance summary

Figure A-6.11 The Workflow Performance Summary shows performance once you have a valid user workflow.

Figure A-6.11 shows the Workflow Performance Summary following the productivity adjustment. Once you have resolved all workflows to a valid workflow solution, you can review the workflow performance summary to evaluate workflow response times for each user site location.

The Workflow Performance Summary will identify queue times for the reduced productivity workflows.

Validated design solution

Figure A-6.12 The CPT Design tab shows performance problems resolved once network bandwidth is increased to accommodate the peak traffic flow.

Figure A-6.12 shows the upgraded CPT Design solution. Once you complete your network suitability analysis, you should work with the network administrator to identify appropriate network bandwidth upgrades.

Best practice: Network bandwidth should be roughly twice the expected peak traffic loads to avoid performance bottlenecks.
Warning: Network traffic utilization over 60 percent could contribute to network contention with low bandwidth connections.
Note: Higher network utilization levels are acceptable with higher capacity connections. Network contention (queue time) is less sensitivity with high bandwidth capacity (bandwidth connections over 45 Mbps). Final bandwidth recommendations should consider cost and performance tradeoffs and traffic variability during peak loads.

Once you agree on bandwidth upgrades, you can enter them in the CPT Design to complete your analysis.

Network performance parameter look-up list

Figure A-6.13 Network performance parameters are identified on the CPT Workflow tab.

Figure A-6.13 shows the key network traffic parameters identified on the CPT Workflow tab. Workflow display chatter, client display traffic, and database traffic columns are established when creating a user workflow and are available in the CPT Workflow tab.

Key workflow network performance inputs provided on the CPT Workflow tab.


Network contribution to Web performance

Network performance counts. Network transport time is a major contribution to web client display response times.

Best practice: Network performance impacts should be considered carefully during design and deployment of web services.


CPT Capacity Planning videos

Chapter 6 Capacity Planning Video will demonstrate impact of network latency on performance, show how to configure the CPT Calculator and Design tab to complete a network suitability analysis. This is an important demo showing how to configure networks and workflows in the Design requirements analysis to represent an enterprise system environment.

Product Architecture

Figure A-7.1 ArcGIS System environment.

GIS Product Architecture provides a foundation for understanding the software components and platform configuration options available for distributed GIS operations. Understanding application architecture alternatives and associated configuration strategies provides a foundation for selecting an appropriate distributed GIS design.

This section will show how to configure the CPT Calculator and Design tabs for the available ArcGIS for Desktop and ArcGIS for Server hardware configurations.

ArcGIS for Desktop workflows

ArcGIS for Server workflows


ArcGIS for Desktop: CPT Calculator configurations

This section shows how to configure the following CPT Calculator ArcGIS for Desktop workflow patterns.

CPT Calculator supports the following workflow configurations.

Note: ArcGIS for Desktop access to an ArcGIS for Server feature service can be shown on the CPT Design tab.]
Best practice: SDE Application Server Connection (ASC) is not supported beyond the ArcGIS 10.2 release..


CPT Calculator workstation

Figure A-7.2 CPT Calculator ArcGIS Desktop Workstation configuration for Direct Connect (DC) DBMS architecture.

Direct Connect (DC) to supported SDE Geodatabase and supported DBMS platforms.

Direct connect architecture platform solution output in rows 16–29.


Figure A-7.3 CPT Calculator configuration of file data source architecture.
Network connection to a selected file data source.

File source architecture platform solution output in rows 16–29.


CPT Calculator Virtual Application Sessions with physical servers

Figure A-7.4 CPT Calculator ArcGIS for Desktop virtual application session in a physical server configuration (DC Architecture).

Direct Connect (DC) to supported SDE Geodatabase and supported DBMS platforms.

Direct connect architecture platform solution output in rows 16–29.


CPT Calculator Virtual Application Sessions with Virtual servers

Figure A-7.5 CPT Calculator ArcGIS for Desktop virtual application session in a virtual server configuration.

Direct Connect (DC) to supported SDE Geodatabase and supported DBMS platforms.

Direct connect architecture platform solution output in rows 16–29.


CPT Calculator High Availability Virtual Application Sessions with Virtual servers

Figure A-7.2 CPT Calculator ArcGIS for Desktop virtual application session in a high availability virtual server configuration.

Direct Connect (DC) to supported SDE Geodatabase and supported DBMS platforms.

Direct connect architecture platform solution output in rows 16–29.


CPT Calculator Virtual Desktop Infrastructure (VDI)

Figure A-7.7 CPT Calculator ArcGIS for Desktop Virtual Desktop Infrastructure in a high availability virtual server configuration.

Direct Connect (DC) to supported SDE Geodatabase and supported DBMS platforms.

Direct connect architecture platform solution output in rows 16–29.


ArcGIS for Desktop: CPT Design configurations

The following ArcGIS for Desktop workflow patterns are supported on the CPT Design tab.

The CPT Design includes several integrated modules used for collecting user requirements information and completing the system design configuration.

CPT Design User Requirements module will be configured to demonstrate the following ArcGIS for Desktop workflows.


CPT Design Workstation Platform Selection

Figure A-7.8 CPT Design hardware configuration module provides 10 tier that can be configured to represent your data center environment.

Platform tier selection will be configured to support the Workstation workflow use cases.


Figure A-7.9 CPT Design software configuration module can be used to assign workflow software components to the previously configured server platform tier.

Software can now be configured to support the Workstation solution.

Identify workflow data sources in column R • Row 6: Small File Geodatabase data source. • Row 7-9: SDE_DBMS data source (supported databases).

Next select software platform assignment

>Web2 and SOC: select GIS Svr platform
>SDE: select Direct Connect
>DBMS: SDEGDB
>Row 8 DB Feature: Select DBMS tier for DBMS platform.
>Row 9 AGS Feature: Select DBMS tier for DBMS platform.
>Row 5 DEFAULT selection


Figure A-7.10 CPT Design provides the final design solution once the user requirements analysis, platform selection, and software platform configuration modules are properly configured.

Once use requirements, platform selection, and software configuration is complete, the CPT completes the system design analysis and provides the design solution.


CPT Design minimum Virtual Application Sessions physical solution

Figure A-7.11 CPT Design platform configuration can be extended to include an additional remote desktop services platform tier.

Add an additional platform tier to support the remote desktop services workflow use cases.


Figure A-7.12 CPT Design requirements analysis can include Citrix workflows that are deployed on central remote desktop service platform tier.

Update workflows and configure software for the RDS use cases.


Figure A-7.13 CPT Design tab updates the system architecture design analysis based on the selected user requirements and design configuration.
Once use requirements, platform selection, and software configuration adjustments are complete, the CPT completes the system design analysis and provides the design solution.


CPT Design Virtual Application Sessions virtual server solution

File:FallCPT14Fig7-15 DsnHACitrixAppVirtualSolution.jpg
Figure A-7.14 CPT Design can be reconfigured to represent virtual application sessions deployed in a virtual server solution by adjusting the platform configuration.

Citrix RDS tier can be deployed in a virtual server environment by updating the platform tier configuration.

Once the platform configuration is updated, CPT completes the design analysis for the Virtual Server configuration.

CPT Design High Availability (HA) Virtual Application Sessions virtual server solution

File:FallCPT14Fig7-15 DesignHACitrixAppVirtualSolutionConfig.jpg
Figure A-7.15 CPT Design can be reconfigured to represent the virtual application sessions deployed in a high availability virtual server solution by adjusting the platform configuration.

Modify platform configuration to identify a HA platform solution.

Once configuration is updated, CPT completes the design analysis for the HA Virtual Server configuration.

CPT Design High Availability (HA) Virtual Desktop Infrastructure solution

Figure A-7.2 CPT Design can be reconfigured to represent virtual desktop sessions deployed in a high availability virtual desktop infrastructure (VDI) solution by adjusting the platform configuration.

Modify RDS platform configuration for a HA VDI configuration.

Once configuration is updated, CPT completes the design analysis for the HA VDI configuration.

Best practice: Virtual Desktops should be supported on a separate host platform from other virtual server machines.


CPT Calculator ArcGIS for Server platform configurations

Figure A-7.17 CPT Calculator ArcGIS for Server single-tier architecture.
The CPT Calculator can be configured for each of the three ArcGIS for Server architecture patterns.


CPT Calculator single-tier configuration

Figure A-7.17 shows a standard ArcGIS for Server 10.2 REST medium web mapping workflow in a single-tier platform configuration. Peak throughput is 100,000 TPH. Service configuration includes an ArcSDE Direct Connect DBMS data source connection.

The CPT Calculator platform architecture configuration is set from a drop-down menu in cell A9. Choices include single, two-tier, and three-tier architecture selections. The single-tier architecture selection supports the Web Adaptor, GIS Server, and DBMS software on a single server platform tier.

Once the CPT Design is properly configured to represent your business requirements and selected hardware, the Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow and the platform section shows the number of required platform nodes and processing loads on the selected platform tier.

CPT Calculator two-tier configuration

Figure A-7.18 CPT Calculator ArcGIS for Server two-tier architecture.

Figure A-7.18 shows a standard ArcGIS for Server 10.2 REST medium web mapping workflow in a two-tier platform configuration. Service configuration includes an ArcSDE Direct Connect DBMS data source connection.

CPT Calculator three-tier configuration

Figure A-7.33 CPT Calculator ArcGIS for Server three-tier architecture.

Figure A-7.33 shows a standard ArcGIS for Server 10.2 REST medium web mapping workflow in a three-tier platform configuration. Service configuration includes an ArcSDE Direct Connect DBMS data source connection.

CPT Calculator three-tier virtual server configuration

Figure A-7.20 CPT Calculator ArcGIS for Server three-tier virtual server architecture.

Figure A-7.20 shows a standard ArcGIS for Server 10.2 REST medium web mapping workflow in a three-tier virtual server platform configuration. Service configuration includes an ArcSDE Direct Connect DBMS data source connection. Host platform tier is shown as a bottom tier below the virtual platform tier. All virtual and host platform selections must be the same platform configuration, since virtual servers will be deployed on the Host platform tier.

CPT Calculator three-tier high availability virtual server configuration

Figure A-7.21 CPT Calculator ArcGIS for Server three-tier high availability virtual server architecture.

Figure A-7.21 shows a standard ArcGIS for Server 10.2 REST medium web mapping workflow in a three-tier HA virtual server platform configuration. HA virtual platform architecture selection in cell A10 and host platform HA selection in cell A30 complete the configuration. Web and GIS Server virtual server tier will include a minimum of two (2) servers, and the DBMS virtual tier will be supported in a failover configuration. The Host Platform will be an N+1 configuration, with capacity for full throughput support with failure of one host platform node.

CPT Design ArcGIS for Server platform configurations

The CPT Design tab provides the capability to represent a complete data center configuration supporting any number of Enterprise workflows from different user locations. ArcGIS for Server recommended platform configuration strategies will be provided for single-tier, two-tier, and three-tier configuration alternatives identified above. Five ArcGIS for Server workflows will be used to represent the user requirements in the CPT Design examples.

The CPT Design includes several integrated modules used for completing the system architecture design. ArcGIS for Server workflow selection is made in the user Requirements Analysis module. Platform tier nicknames (followed by a colon) and selected hardware platform can be modified to represent your data center deployment configuration. Software platform configuration is identified by selecting a platform nickname from the highlighted software component drop-down list on each workflow row. Data source selection is made for each workflow row.

CPT Design ArcGIS for Server single-tier platform configuration

Figure A-7.22 CPT Design ArcGIS for Server single-tier platform configuration

The single tier software configuration would host the Web, GIS Server, and DBMS data source all on a single platform tier.

Once the CPT Design is properly configured to represent your business requirements and selected hardware, the Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow and the platform section shows the number of required platform nodes and processing loads on the selected platform tier.

CPT Design ArcGIS for Server single-tier hardware tier configurations

Figure A-7.22 shows a Web single-tier hardware configuration.

Platform tier nicknames (followed by a colon) can be modified to represent your deployment environment. The platform nicknames must be updated before completing the software configuration assignments.


CPT Design ArcGIS for Server single-tier software configuration
Figure A-7.23 CPT Design ArcGIS for Server single-tier software configurations

Figure A-7.23 shows the five standard ArcGIS for Server workflow configurations. Workflow software components are identified in row 4, columns J through R. User workflow is selected in column B. Software components for each workflow row are highlighted based on workflow selection. Web, SOC, and DBMS software are assigned to the GIS platform tier.

Software platform configuration is identified by selecting a platform nickname from the highlighted software component drop-down list on each workflow row. The default platform selection is provided on row 5. SDE Direct Connect is identified for all default SDE components by selecting default platform in row 4. The configured platform will be highlighted in RED if existing nickname is not on the platform drop-down list.

Data source selection for each workflow row is selected from a drop-down list in column R. Drop-down list contains vector data sources for mapping workflows and imagery data formats for imagery workflows.

CPT Design ArcGIS for Server single-tier Enterprise solution
Figure A-7.24 ArcGIS for Server single-tier CPT Design solution

Figure A-7.24 provides a full view of the CPT Design solution for the same five ArcGIS for Server workflows.

The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the selected platform tier.

CPT Design ArcGIS for Server two-tier platform configuration

Figure A-7.25 CPT Design ArcGIS for Server two-tier platform configuration
The two tier software configuration would normally host the Web and GIS Server on one platform tier, and the DBMS servers on separate platform tier.

The CPT Design workflows include three different data sources, one being an SDE Geodatabase (SDEGDB), the second a tabular business database management system (DBMS), and the third a file data source. Each data source will be represented on a dedicated platform tier for modeling purposes. The file data source is represented in the bottom row and platform sizing is based on network interface bandwidth requirements. Column A identifies the different user workflows:

Once the CPT Design is properly configured to represent your business requirements and selected hardware, the Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow and the platform section shows the number of required platform nodes and processing loads on the selected platform tier.

CPT Design ArcGIS for Server two-tier hardware configuration

Figure A-7.25 shows a Web single-tier hardware configuration.

Platform tier nicknames (followed by a colon) can be modified to represent your deployment environment. The platform nicknames must be updated before completing the software configuration assignments.


CPT Design ArcGIS for Server two-tier software configurations
Figure A-7.26 CPT Design ArcGIS for Server two-tier software configurations

Figure A-7.26 shows the five standard ArcGIS for Server workflow configurations. Workflow software components are identified in row 4, columns J through R. User workflow is selected in column B. Software components for each workflow row are highlighted based on workflow selection. Web and SOC software are assigned to the GIS Svr platform tier. DBMS software is assigned to the SDEGDB platform tier for rows 7 and 8 and the DBMS platform tier for row 9. The two workflows with file data sources include rows 6 and 10 (no DBMS server assignment required).

Software platform configuration is identified by selecting a platform nickname from the highlighted software component drop-down list on each workflow row. The default platform selection is provided on row 5. SDE Direct Connect is identified for all default SDE components by selecting default platform in row 4. The configured platform will be highlighted in RED if existing nickname is not on the platform drop-down list.

Data source selection for each workflow row is selected from a drop-down list in column R. Drop-down list contains vector data sources for mapping workflows and imagery data formats for imagery workflows.

CPT Design ArcGIS for Server two-tier Enterprise solution
Figure A-7.27 ArcGIS for Server two-tier CPT Design solution

Figure A-7.24 provides a full view of the CPT Design solution for the same five ArcGIS for Server workflows.

The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the selected platform tier.

CPT Design ArcGIS for Server three-tier platform configuration

Figure A-7.28 CPT Design ArcGIS for Server three-tier platform configuration
The three tier software configuration would normally host the Web server on one platform tier, the GIS Server on a second platform tier, and the DBMS server on separate database platform tier.

Once the CPT Design is properly configured to represent your business requirements and selected hardware, the Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow and the platform section shows the number of required platform nodes and processing loads on the selected platform tier.

CPT Design ArcGIS for Server three-tier hardware configuration

Figure A-7.28 shows an ArcGIS for Server three-tier hardware configuration.

Platform tier nicknames (followed by a colon) can be modified to represent your deployment environment. The platform nicknames must be updated before completing the software configuration assignments.


CPT Design ArcGIS for Server three-tier software configurations
Figure A-7.29 CPT Design ArcGIS for Server three-tier software configurations

Figure A-7.29 shows the five standard ArcGIS for Server workflow configurations. Workflow software components are identified in row 4, columns J through R. User workflow is selected in column B. Software components for each workflow row are highlighted based on workflow selection. Web software is assigned to the Web server, SOC software is assigned to the GIS platform tier, and DBMS software is assigned to the SDEGDB platform tier for rows 7 and 8 and the DBMS platform tier for row 9.

Software platform configuration is identified by selecting the platform nickname from the highlighted software component drop-down list on each workflow row. The default platform selection is provided on row 5. SDE Direct Connect is identified for all default SDE components by selecting default platform in row 4. The configured platform will be highlighted in RED if existing nickname is not on the platform drop-down list.

Data source selection for each workflow row is selected from a drop-down list in column R. Drop-down list contains vector data sources for mapping workflows and imagery data formats for imagery workflows.

CPT Design ArcGIS for Server three-tier Enterprise solution
Figure A-7.30 ArcGIS for Server three-tier platform solution

Figure A-7.31 provides a full view of the CPT Design solution for the same five ArcGIS for Server workflows.

The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the selected platform tier.

CPT Design ArcGIS for Server three-tier virtual server Enterprise solution

Figure A-7.31 ArcGIS for Server three-tier virtual server CPT Design solution

Figure A-7.31 provides the platform view of the CPT Design solution for the same five ArcGIS for Server workflows.

>Select virtual platform, number of core/node, and Host platform assignment.
>Host platform tier are located at the bottom below the virtual platform tier.
>Virtual tier must have same platform selection as assigned Host platform tier.

The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the selected platform tier.

CPT Design ArcGIS for Server three-tier high availability virtual server Enterprise solution

Figure A-7.32 ArcGIS for Server three-tier high availability virtual server CPT Design solution

Figure A-7.32 provides the platform view of the CPT Design solution for the same five ArcGIS for Server workflows.

The Workflow Performance Summary shows the software service time distribution and expected client display response time for each workflow, while the platform section shows the processing loads on the selected platform tier.

Concluding Remarks

There are several factors that should be considered when establishing your enterprise data center architecture. Many of these factors are determined based on business needs and standard IT operating procedures.

The primary focus for Esri system architecture design services is to identify hardware and infrastructure resources that satisfy user productivity needs during peak GIS system loads. This effort focuses on the primary production hardware and available network infrastructure bandwidth required to support GIS operations.

Figure A-7.33 CPT Design Platform Module

Other factors contribute to the final system configuration. These factors include provisions for system maintenance, updates, configuration control, software licensing, and security. System requirements often include hardware provisions for application development, system test, production staging, background processing (i.e. map cache maintenance and replication services), system backup, and security. System migration will normally include continued support for legacy operations while introducing new technology, often on separate hardware environments.

The CPT Design tab provides a framework for modeling enterprise operations. Figure A-7.33 provides an overview of the adaptive CPT Design platform module.

An Enterprise GIS design includes business, application, data, and technical architecture requirements. The Capacity Planning Tool provides a framework that models enterprise GIS performance and scalability, integrating the full range of Enterprise system design requirements into a solution that represents your GIS production needs.

CPT Capacity Planning videos

Chapter 7 Capacity Planning Video will show how to configure the CPT to represent your data center platform architecture selection.

Platform Performance

Figure A-8.1 Platform performance baseline
Selecting the right hardware will improve user performance, reduce overall system cost, and establish a foundation for building effective GIS operations. Selecting the wrong hardware can contribute to implementation failure - spending money on a system that will not support your business needs. Figure A-8.1 shows the changes in platform performance over the past 10 years.

This section will introduce the CPT Hardware tab, use the CPT to evaluate hardware platform best buy decision, and use the CPT Platform Capacity Calculator and CPT Calculator for platform sizing.


CPT Hardware tab

Figure A-8.2 CPT Hardware tab provides a lookup table used by the CPT models to complete the capacity planning analysis
Figure A-8.2 shows the CPT Hardware tab that includes a list of Desktop and Server SPEC CPU platform benchmark baseline values used as a lookup table by the CPT Calculator, Design, Test, and Favorites tabs. The SPEC benchmark values are used to adjust baseline service times to selected platform service times for capacity planning analysis.

Published vendor benchmark values are used to identify relative throughput and performance for selected hardware platforms. Platforms are arranged by vendor and year in two lookup lists. Desktop candidates are located at the top of the list. Server candidates are located at the bottom of the list. Project platform candidates are located in the middle of the list and included with the Desktop and Server list selections.

Primary platform values are entered in the WHITE cells (Processor, # of Cores, Core/Chip, MHz, SPECint_rate2006 baseline). COLORED cell values are generated from the WHITE cell entries (Hardware Platform Selection, Per core SPECint_rate2006 value, Total chips). Additional columns include vendor and WATTs information.

The SPEC Web site is the primary source for the platform performance metrics. Information from the SPEC Web site is entered into the CPT Hardware tab for capacity planning. Copy of the SPEC benchmark information is provided in a HardwareSPEC Excel workbook for easy access.

HardwareSPEC Excel Workbook

Figure A-8.3 HardwareSPEC Excel Workbook includes a snapshot copy of the vendor published SPEC Web Site benchmark values
Figure A-8.3 provides a view of the HardwareSPEC workbook. The Esri Capacity Planning Tool release site shares a HardwareSPEC workbook with an Excel table of platform relative performance values from the published SPECrate_integer benchmarks.

The HardwareSPEC workbook contains a SRint2000 tab and a SRint2006 tab. The SRint2000 tab includes all vendor published SPECrate_int2000 benchmarks available on the SPEC site (SPEC stopped publishing new SRint2000 benchmarks in January 2007). All the new platform benchmarks are now published on the SPECrate_integer2006 site (SRint2006 tab). The last date the benchmark tab was updated is shown with the link name. A hot link to the SPEC site is included on the top of the Capacity Planning Tool (CPT) hardware tab.

The HardwareSPEC workbook tabs include an additional column (baseline/core) that I add to the table. This column identifies the processing performance of an individual core, a value that is used to estimate relative platform processing performance for a single sequential display (estimate of the relative platform speed). The relative processing performance per core values will be used in this chapter to comparing user display performance.

Adding a new platform to the CPT Hardware tab

Figure A-8.4 CPT Hardware tab with a new Dell Demo server added to the Project Platform Candidate lookup list
New hardware platform benchmark values are published on the SPEC Web site each month throughout the year, so the platform you need for your design analysis may not be included in your version of the CPT. You can locate the new benchmark values on the SPEC Web site and then add them to your CPT Hardware tab.

Figure A-8.4 highlights the entries you will need to make to the CPT Hardware tab.

To add a new Server to the CPT Hardware tab, first create a new row template by copying one of the existing Platform rows and Insert Copied Cells to create a new row in the Project Platform Candidate section. Enter the processor name, # of Cores, Core/Chip, MHz, and the SPECint_rate2006 baseline value for the new server (Type new entries in the white cells only). The colored cells include formulas and will be completed as you enter the new values in the white cells.

Once you have completed your entries, the new server will be available for selection in all CPT Platform Selection dropdown lists.

CPT used to evaluate best buy

CPT is designed to automate the system architecture design analysis. The system architecture design analysis translates user business requirements to appropriate hardware platform solutions. Once you know your business requirements, the CPT can be used to identify your optimum platform selection.

Establishing business needs

Proper hardware selection depends on a clear understanding of your business needs. Figure A-8.5 will show how to select the optimum platform for publishing ArcGIS 10.2 REST mapping services.

Figure A-8.5 CPT Calculator tab configured for use in evaluating server platform candidates.

Business workflow requirements

Hardware Platform candidates include the following:

Platform pricing analysis

Figure A-8.6 provides an overview of the platform pricing analysis.

Figure A-8.6 Overview of the best buy hardware platform selection analysis.

Hardware and Software pricing analysis

Xeon E5-2690 platform has the lowest hardware cost per core without considering software pricing.

Warning: Selecting a server platform without evaluated what you need to satisfy your business requirements can lead to the wrong hardware selection.

Completing the capacity planning analysis

Figure A-8.7 CPT Calculator Xeon E3-1280v2 and E5-2643 platform solution summaries.
Figure A-8.7 shows the best buy CPT Calculator sizing evaluation of the Xeon E3-1280v2 and E5-2643 platforms.

Business workflow requirements are used to identify the required server cores for each analysis.

Xeon E3-1280v2 platform

Xeon E5-2643 platform

Figure A-8.8 shows the CPT Calculator evaluation of the Xeon E5-2667 and E5-2690 platforms.

Figure A-8.8 shows the buest buy CPT Calculator sizing evaluation of the Xeon E5-2667 and E5-2690 platforms.

Business workflow requirements are used to identify the required server cores for each analysis.

Xeon E5-2667 platform

Xeon E5-2690 platform

Best Buy:


CPT Design platform analysis summary report

Figure A-8.6 shows the CPT Calculator evaluation of the Xeon E3-1280v2 and E5-2643 platforms.

Figure A-8.9 CPT Design composite platform solution summary.
Figure A-8.9 shows how the CPT Design tab can be used to evaluate all servers in a single report.

CPT Design is configured to represent the four different platform environments.

Complete your system design analysis before making your hardware selection.

CPT Platform Sizing Analysis

Platform Capacity Calculator platform sizing

Figure A-8.10 Platform Capacity Calculator Platform Sizing Summary
CPT Platform Capacity Calculator can be used for a simple platform sizing analysis as shown in Figure A-8.10.

Select the platform for evaluation on the Platform Capacity Calculator located at the bottom of the CPT Hardware tab. Select if you want results in peak users or transactions per hour in column C. Peak throughput estimate for light and medium complexity workflows is provided for the workflows selected for the workflow display. The Platform Capacity Calculator provides a quick rough platform sizing estimate for a single workflow load.

CPT for Windows Terminal Server platform sizing

Figure A-8.11 CPT Calculator Windows Terminal Server Platform Sizing
CPT Calculator tab can be used for Windows Terminal Server platform sizing as shown in Figure A-8.11.

Select the workflow description that represents your Citrix server performance targets. AGD102 Citrix software profile with MXD Map Document is used for ArcGIS for Desktop Windows Terminal Server platform sizing. Select appropriate density, %DataCache, Complexity, and display Resolution for your average workflow use case. Selecting the right software technology performance factors to represent your business workflow is discussed in [Software Performance chapter].

Identify your peak user requirements and most common data source. Identify your planned platform architecture (2 tier, minimum or high availability, DC), and Select your hardware platform choice.

The recommended platform solution is generated by Excel once you enter your business requirements and make your hardware selections. You can try different platform configurations and experiment with different workflow complexities. Peak concurrent users per node for Windows Terminal Server are provided in cell J10.

The CPT Calculator tab can be used for single workflow platform sizing. The CPT Design tab should be used for more detailed enterprise design planning.

CPT for Windows Terminal Server memory guidelines

Recommended platform memory is provided in CPT Calculator cell I10 and on the CPT Design platform tier in column C. Formula used to calculate memory recommendations (rollover x SPEC throughput / 13.4) adjusts for peak concurrent user loads, workflow complexity, and selected platform configuration. Each platform tier shows the average user process size for the recommended memory guideline in Column P and includes a cell to input custom process memory requirements if needed.

CPT for ArcSDE Geodatabase platform sizing

CPT Calculator tab can be used for ArcSDE Geodatabase platform sizing as shown in Figure A-8.121.

Figure A-8.12 ArcSDE Geodatabase platform sizing

Select the workflow description that represents your user performance targets. AGD wkstn, AGD citrix, and a variety of AGS software profiles are available. MXD Map Document is used for ArcGIS Desktop profiles and MSD is used for most ArcGIS Server workflows. Select appropriate density, %DataCache, Complexity, and display Resolution for your average workflow use case. Selecting the right software technology performance factors to represent your business workflow is discussed in [Software Performance chapter].

Identify your peak user requirements and the SDE_DBMS data source. Select a 2 tier platform architecture and your SDE GDB hardware platform choice.

The recommended platform solution is generated by Excel once you enter your business requirements and make your hardware selections. You can try different platform configurations and experiment with different workflow complexities. Peak concurrent users per node for the SDE Geodatabase server are provided in cell J11.

The CPT Calculator tab can be used for single workflow platform sizing. The CPT Design tab should be used for more detailed enterprise design planning.

CPT for ArcSDE Geodatabase Server memory guidelines

Recommended platform memory is provided in CPT Calculator cell I11 and on the CPT Design platform tier in column C. Formula used to calculate memory recommendations (4 x rollover x SPEC throughput / 13.4) adjusts for peak concurrent DBMS connections, database complexity, and selected platform configuration. Each platform tier shows the average DBMS connection size for the recommended memory guideline in Column P and includes a cell to input custom connection memory requirements if needed.

CPT for ArcGIS for Server platform sizing

CPT Calculator tab can be used for ArcGIS for Server platform sizing as shown in Figure A-8.13.

Figure A-8.13 ArcGIS for Server platform sizing

Select the workflow description that represents your user performance targets. AGS REST, AGS KML, AGS WMS, AGS SOAP, and AGS Imagery software profiles are available. MXD Map Document is used for most ArcGIS for Server map services. Select appropriate density, %DataCache, Complexity, and display Resolution for your average workflow use case. Selecting the right software technology performance factors to represent your business workflow is discussed in [Software Performance chapter].

Identify your peak user requirements and your selected data source. Select your platform architecture and your hardware platform choice.

The recommended platform solution is generated by Excel once you enter your business requirements and make your hardware selections. You can try different platform configurations and experiment with different workflow complexities. Peak concurrent users per node for the SOC server are provided in cell J10.

The CPT Calculator tab can be used for single workflow platform sizing. The CPT Design tab should be used for more detailed enterprise design planning.

CPT Web and ArcGIS for Server memory guidelines

Web and ArcGIS for Server memory guidelines are generated based on recommended peak active concurrent service instance (SOC) configurations supported by the selected platform configuration. The general guideline is 3 GB memory per server core. 3 GB memory would support up to 15 concurrent 100 MB active SOC service instances, well above the recommended target configuration of 3-5 active service instances per core for peak system throughput.

Warning: Sufficient memory must be available to support the peak number of active concurrent SOC processes. Additional memory may be required for GIS Server sites that support a high number of active concurrent SOC processes (more than 15 service instances per core)

Memory recommendations are provided on the CPT Calculator tab in cells I9 and I10, and on the CPT Design tab on each platform tier in column C. Average process size is provided on each tier in column P along with a cell to enter a custom process size if required.

CPT virtual server host platform memory guidelines

Virtual server host platform memory guidelines are generated based on the total assigned virtual server memory requirements plus additional 1 GB per core for hypervisor memory. Minimum host platform recommended memory would be 4 GB per core.

CPT Capacity Planning videos

Chapter 8 Capacity Planning Video shows how to complete your platform selection, how to add new servers to the CPT, how to complete a best buy analysis, and how to make the right platform selection for your system design.

Information Security

No CPT activities

Performance Management

Figure A-10.1 Performance management involves building a design solution based on appropriate workflow performance targets and managing compliance throughout design and implementation to deliver within those targets.
Esri started developing simple system performance models in the early 1990s to document our understanding about distributed processing systems. These system performance models have been used by Esri system design consultants to support distributed computing hardware solutions since 1992. These same performance models have also been used to identify potential performance problems with existing computing environments.

The Capacity Planning Tool was introduced in 2008 incorporating the best of the traditional client/server and web services sizing models providing an adaptive sizing methodology to support future enterprise GIS operations. The capacity planning tool methodology is easy to use and provides metrics to manage performance compliance during development, initial implementation, and system delivery.

Figure A-10.1 shows how system architecture design models can be used for performance management.

CPT Design workflow productivity adjustment

CPT Design productivity adjustment (RESET ADJUST) is an important function used to model system performance. The CPT RESET ADJUST function can be used to identify valid user productivity when user productivity is constrained by system performance bottlenecks. The RESET ADJUST function is also used to reserve system resources for batch processing workflows where productivity is constrained by the system configuration.

CPT Design user workflow productivity adjustment

Figure A-10.2 CPT Design shows business requirements for ArcGIS for Desktop workflows deployed on a single Windows Terminal Server platform that does not satisfy user productivity needs.

Figure A-10.2 shows the CPT Design tab identifying an invalid design solution.

Peak concurrent user loads are not supported by the selected hardware solution.

User workflow requirements include Citrix editors and viewers hosted by a centralized WTS Platform communicating through the data center WAN and Internet gateway connections.

The single Citrix WTS server platform (Xeon E3-1280v2 4-core (2 chip) 3600 MHz) is showing an overcapacity load of 105.6 percent.

This is an invalid solution.


User productivity is reduced to identify maximum valid solution
Figure A-10.3 CPT Design shows user productivity reduced identifying maximum workflow performance within restricted server capacity.

Figure A-10.3 shows the CPT Design tab solution following the workflow productivity adjustment.

CPT Design RESET ADJUST function is used to identify maximum valid solution.

  • Function "blinks" between positive and negative calculated think time values.
  • Calculated think times = Minimum think times.
  • Peak concurrent user cells turn green to show valid workflows.

CPT Design shows the impact of not having adequate server capacity to handle identified workflow loads.

Best practice: System design should be upgraded to satisfy user productivity needs.


CPT Design productivity adjustment used to represent a batch process

Figure A-10.4 CPT Design configured with a batch workflow. Batch process has zero (0) think time and ADJUST function must be used to identify batch loads.

Figure A-10.4 shows a CPT Design configured with a single batch process.

Best practice: Workflow selection should have same load profile (client, web, GIS server, SDE, DBMS) as the batch process you wish to model. Total processing time is not important for modeling batch loads.

Platform configuration is a two tier configuration

Warning: This is an invalid design.


Figure A-10.5 shows a CPT Design batch process valid design solution.

Figure A-10.5 Batch process productivity calculated using the CPT Design RESET ADJUST function.

The batch process productivity must be computed to identify a valid workflow. Productivity will depend on the server loads and available system resources. A single batch process can take advantage of only one processor core.

Peak batch instances must be identified in terms of number of Users (column C) or number of Clients (column D).

CPT Design RESET ADJUST function is used to identify maximum valid solution.

Total batch process instances can be identified in Column D except when TPH is selected in cell D6 (interprets selection as transactions per hour).

Examples of batch process workflows:

Best practice: Recommended design practice - any heavy function (runs more than 30 seconds) that might be requested by several users at a time should be configured as a batch process (network services). Processing queue must be established for user work request input. Each batch instance (network service) will process requests sequentially based on available processor resources. User can be notified once their work request is services.

CPT Design evaluation of physical and virtual multi-core performance

Figure A-10.6 The CPT Design tab is used to demonstrate peak throughput performance for four different platform configurations.

Figure A-10.6 shows how platform queue time contributes to server performance.

The CPT Design is configured to represent 4 different test environments. Same workflow and physical server platforms are used for each test case.

Each test environment is supported by a single platform tier. Each environment includes the same number of processor core (4 core). The four test configurations include the following:

Each workflow load was increased until display response time reached two seconds.

;Peak system loads with display response time = 2 seconds

  • Peak throughput = 98,380 (98 percent of physical 4-core throughput)
  • Platform utilization = 96.2 percent
  • Peak throughput = 100,285 (highest throughput for all configurations)
  • Platform utilization = 98.1 percent
  • Peak throughput = 89,060 (89 percent of physical 4-core throughput)
  • Platform utilization = 95.8 percent
  • Peak throughput = 83,220 (93 percent of Virtual 2-core throughput)
  • Platform utilization = 97.7 percent

Virtual server performance overhead increases service time for multi-core servers. As a result, peak throughput performance degrades with increasing number of virtual core.

Initial CPT releases applied 10 percent processing overhead per core for virtual server environments. More recent virtual environments do not require as much overhead, and CPT virtual server overhead planning factors were reduced with the July 2013 release.

Arc13CapacityPlanning0701 applied virtual server overhead:

Best practice: For physical server platforms with same per core performance, more cores per server provides more throughput. For virtual server platforms with reduce per core performance, fewer cores per server provides more throughput.
Warning: More cores per server improves throughput only when display service times remain constant between configurations.

Performance Validation

Planning provides the first opportunity for building successful GIS operations. Getting started right, understanding your business needs, understanding how to translate business needs to network and platform loads, and establishing a system design that will satisfy peak user workflow requirements is the first step on your road to success.

Planning is an important first step – but it is not enough to ensure success. If you want to deliver a project within the initial planning budget, you need to identify opportunities along the way to measure progress toward your implementation goal. Compliance with performance goals should be tracked throughout initial development, integration, and deployment - integrate performance validation measurements along the way. Project success is achieved by tracking step by step progress toward your implementation goal, making appropriate adjustments along the way to deliver the final system within the planned project budget. The goal is to identify problems and provide solutions along the way - the earlier you identify a problem the easier it will be to fix. System performance can be managed like any other project task. We showed how to address software performance in Chapter 3, network performance in Chapter 5, and platform performance in Chapter 7. If you don’t measure your progress as these pieces come together, you will miss the opportunity to identify and make the appropriate adjustments needed to ensure success.

There are several opportunities throughout system development and deployment where you can measure progress toward meeting your performance goals. The CPT Test tab includes four tools you can use to translate live performance measurements to workflow service times – the workflow performance targets used to define your initial system design.

Map display render times

In Chapter 3 we shared the important factors that impact software performance. For Web mapping workflows, map complexity is the primary performance driver. Heavy map displays (lots of dynamic map layers and features included in each map extent) contribute to heavy server processing loads and network traffic. Simple maps generate lighter server loads and provided users with much quicker display performance. The first opportunity for building high performance map services is when you are authoring the map display.

There are two map rendering tools available on the CPT Test tab that use measured map rendering time to estimate equivalent workflow service times. One tool is available for translating ArcGIS for Desktop map rendering times (MXD) and the other tool is for translating ArcGIS for Server map service rendering times (MSD). With both tools, measured map rendering time is translated to workflow services times that can be used by the CPT Calculator and Design tabs for generating your platform solution. The idea is to validate that your map service will perform within your planned system budget by comparing the workflow service times generated from your measured rendering times with your initial workflow performance targets. If the service times exceed your planned budget, you should either adjust the map display complexity to perform within the initial planning budget or increase your system performance budget. The best time to make the map display complexity adjustment is during the map authoring process. Impacts on the project budget can be evaluated and proper adjustments made to ensure delivery success.

Measured MSD render time

Figure A-10.7 The CPT Test validation tool used for translated measured map service MSD render times to workflow service times.

Figure A-10.7 shows a tool you can use to translate measured MSD render time to workflow service times. MSD render time can be measured when publishing your map service using the service editor preview tool.

Warning: Make sure to measure a map location that represents the average map complexity or higher within your service area extent and adjust preview to average client display resolution. Use a local FGDB data source to collect proper measurement.
Note: Pan or Zoom of the ArcGIS for Server service editor preview window will provide render time for fresh dynamic display

The Measured Performance tool can be used to generate workflow service times from a measured MSD render time.

Baseline workflow service time is provided in range D15:21.


Measured MXD render time

Figure A-10.8 The CPT Test validation tool used for translated measured map service MXD render times to workflow service times.

Figure A-10.8 shows a tool you can use to translate measured MXD render time to workflow service times. MXD render time can be measured using the MXDPerfStat ArcScript performance measurement tool.

Warning: Make sure to measure a map location that represents the average map complexity or higher within your service area extent. Adjust map display to average client display resolution. Use a local FGDB data source to collect proper measurement.
Note: MXDPerfStat tool uses the Windows rendering engine to measure display performance at a selected location and map display extent, identifying render time for each scale included in the selected map document

The CPT Measured Performance tool can be used to generate workflow service times from the measured MXD display render time.

Arc12 workflow service time is provided in range D15:21.

Measured throughput and platform utilization

Figure A-10.9 The CPT Test validation tool used for translated measured map service throughput and platform utilization to workflow service times.

If you know your platform configuration, your measured peak workflow throughput, and the associated platform utilization the CPT can calculate the workflow service times. The Test tab translation tools can be used to input throughput (transaction per hour), the platform configuration (server platform selection), and the measured platform utilization and excel will translate these inputs to equivalent workflow service times. Figure A-10.9 shows the inputs required for completing this transaction.

Best practice: Performance metrics can be collected from benchmark test or live operations.
Warning: Make sure all measurements are collected for the same loads at the same time.

The Live Results tool can be used to generate workflow service times from throughput and utilization measurements.

Arc12 workflow service time is provided in range G3:10.

Translate measured traffic to workflow transaction Mbpd.


Measured peak concurrent users and platform utilization translator

Figure A-10.10 CPT Test validation tool used for translated map service peak concurrent users and platform utilization to workflow service times.

If you don’t have measured throughput, concurrent users working on the system can be used to estimate throughput loads. This is a valuable tool for using real business activity to validate system capacity (business units identify peak user loads and IT staff identify server utilization observed during these loads). The Test tab can be used to input throughput (peak concurrent users), the platform configuration (server platform selection), and the measured platform utilization and excel will translate these inputs to equivalent workflow service times. Figure A-10.10 shows the inputs required for completing this transaction.

Best practice: Analysis assumes peak users are working at web power user productivity (6 DPM) over a reasonable measurement period (10 minutes).
Warning: Make sure all measurements are collected for the same loads at the same time.

The Live Results tool can be used to generate workflow service times from peak concurrent users and utilization measurements.

Arc12 workflow service time is provided in range G3:10.

Translate measured traffic to workflow transaction Mbpd.


Move Test tab derived workflow service times to project workflows.

Figure A-10.11 Workflows generated on the CPT Test tab can be transferred to your project workflows on the CPT Workflow tab.

The CPT Workflow tab is where the results of your performance validation efforts come together. Figure A-10.11 shows how each of these test results can be brought together, along with the original workflow service times, to validate that you are building a system that will perform and scale within your established project performance budget.

Moving workflows to your Project Workflow list.

Best practice: Performance management, including performance validation throughout development and system delivery, is the key to implementation success. It is important that you identify the right technology and establish reasonable performance goals during your initial system design planning. It is even more important that you monitor progress in meeting these goals throughout final system development and delivery.

CPT Capacity Planning videos

Chapter 10 Capacity Planning video shows how to use the CPT Design adjust function to identify performance impact of undersized systems, how to represent a batch process in your design, and how to use the CPT to translated measured system performance to workflow services times to validate deployed services are performing within the performance budget established in your system design.

Previous Editions

Capacity Planning Tool 34th Edition
Capacity Planning Tool 33rd Edition
Capacity Planning Tool 32nd Edition
Capacity Planning Tool 32nd Edition
Capacity Planning Tool 31st Edition
Capacity Planning Tool 30th Edition
Capacity Planning Tool 29th Edition
Capacity Planning Tool 28th Edition
Capacity Planning Tool 27th Edition

System Design Strategies (select here for table of contents)
1. System Design Process 2. GIS Software Technology 3. Software Performance 4. Server Software Performance
5. GIS Data Administration 6. Network Communications 7. GIS Product Architecture 8. Platform Performance
9. Information Security 10. Performance Management 11. System Implementation 12. City of Rome
A1. Capacity Planning Tool B1. Windows Memory Management Preface (Executive Summary) SDSwiki What's New

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

Navigation
Need Help
Toolbox
Share This Page