ArcGIS Enterprise Systems: Performance and Scalability

Transcription

1 2013 Esri International User Conference July 8 12, 2013 San Diego, California Technical Workshop ArcGIS Enterprise Systems: Performance and Scalability Frank Pizzi fpizzi@esri.com Andrew Sakowicz ASakowicz@esri.com Esri UC2013. Technical Workshop op.

2 Introductions Target audience - GIS, DB, System administrators - Testers - Architects - Developers - Project managers Level - Intermediate

3 Objectives Performance engineering concepts and best practices Technical - Solution performance factors - Tuning techniques - Performance testing - Capacity planning Managerial - Skills - Level of effort and costs - Risks - ROI

4 Agenda Introduction Definitions Process Requirements Performance Factors Software Performance Factors - Hardware Performance Tuning Performance Testing Monitoring Capacity Planning

5 Definitions

6 Definitions Performance The speed at which a given operation occurs E.g. Request response time measured in seconds

7 Definitions Scalability The ability to increase output and maintain acceptable performance Examples - Capacity 10 maps/sec and response time 1 second - Capacity 1000 cars/hrs and speed 55 mph

8 Definitions Capacity The maximum level of output the system can produce At capacity Over capacity

9 Definitions Bottleneck Resource(s) limiting the performance or capacity Low load Think of : lanes - as CPU processor toll booths as ArcGIS Server instances cars - as map requests High load

10 Definitions Step Load and Response Time Step Load (users) Response Time (sec) time

11 Definitions Throughput (request/hr) Step Load (users) Throughput(req/hr) Response Time (sec) time

12 Definitions Resource utilization: CPU, Memory, Network Step Load (users) Throughput(req/hr) CPU Utilization (%) Network used (Mbps) Response Time (sec) Memory used (Mb) time

13 Definitions Capacity User load Throughput(req/hr) CPU Utilization (%) Network used (Mbps) Response Time (sec) Capacity (~ 85% utilization) Memory used (Mb) Content length (bytes) Time

14 Response time breakdown (sec)

15 Response time breakdown (%)

16 Process

17 Esri Process and Tools Holistic approach

18 Tools owner:enterpriseimp Show ArcGIS Desktop Content

19 Tools System Designer (MS 2013) System Test (Beta) System Monitor (Beta) System CPU Network Test Mxdperfstat Database Trace Tools ASlog

20 Testing process Application GIS Services Infrastructure: Hardware and Software

21 Required skill set Configuration, Tuning, Testing Performance Tuning Sizing (Hardware and Software) Performance Testing

22 Capacity Planning Tools

23 Requirements: Performance Service-Level Agreement

24 Requirements Performance engineering addresses quality attributes Functional Requirements Quality Attribute Requirements Visualization Analysis Workflow Integration Availability Performance & Scalability Security

25 Requirements Define System Functions - What are the functions that must be provided? Define System Attributes - Nonfunctional requirements should be explicitly defined Risk Analysis - An assessment of requirements - Intervention step designed to prevent project failure Analyze/Profile Similar Systems - Design patterns - Performance ranges

26 Performance Factors - Software

27 Performance Factors - Software Application Type (e.g., mobile, web, desktop) Stateless vs. stateful (ADF) Design - Chattiness - Data access (feature service vs. map service) Output image format

28 Performance Factors - Software Application Types rprise-gis/01n htm

29 Performance Factors - Software Application Security rprise-gis/01n htm -

30 Performance Factors - Software GIS Services ArcSOC instances Max Instances =~ #CPU Cores e.g. 2, 8 core machines, set max instance to 8 If max SOC instances are under configured, system will not scale.

31 Performance Factors - Software GIS Services Map Service Source document (MXD) optimizations Keeping map symbols simple - Setting scale dependency - Avoiding multilayer, calculation-dependent symbols - Spatial index - Avoiding reprojections on the fly - Optimizing map text and labels for performance - Using annotations - Cost for Maplex and antialiasing - Using fast joins (no cross database joins) - Avoiding wavelet compression-based raster types (MrSid, JPEG 2000)

32 Performance Factors - Software Map service Performance related to number of features and vertices Response Time (sec) Number of features

33 Performance Factors - Software Geodatabase Keep delta tables and versioning tree small - Reconcile and post - Compress - Synchronize replicas Rebuild indexes Update statistics

34 Performance Factors - Software Data storage Typically a low impact Small fraction (< 20%) of total response time 140,000 Low Complexity Map: Throughput vs. data source 120,000 Throughput (Tr/Hr) 100,000 80,000 60,000 40,000 20,000 0 FGDB_Local_URL SHP_Local_URL Ora11g_AS_URL SQLSvr_AS_URL Postgres_AS_URL

35 Performance Factors - Software Data source location Local to SOC machine UNC (protocol + network latency overhead) High Complexity Map Service: Local vs. UNC (1 SOC) Throughput (Tr/Hr) FGDB_Local FGDB_UNC SHP_Local SHP_UNC Data Source Location All disks being equal, locally sourced data results in better throughput.

36 Performance Factors - Software ArcMap settings Default geodatabase Display cache Performance degradation when high network latency Typical case: global companies using roaming profile

37 Performance Factors - Hardware

38 Performance Factors - Hardware Hardware Resources - CPU - Network bandwidth - and latency - Memory - Disk Most well-configured and tuned GIS systems are processor bound.

39 Performance Factors - Hardware CPU Processor Speed Specrate.org

40 Demo CPU Processor Speed 1. System CPU 2. PassMark

41 Impact of CPU speed CPU score new laptop old laptop Response (sec) new laptop old laptop Ratio RT TH Score Throughput max (tr/sec) new laptop old laptop

42 Performance Factors - Hardware Capacity planning 1. User load: Concurrent users or throughput 2. Operation CPU service time (model) performance 3. CPU SpecRate subscript t = target subscript b = benchmark ST = CPU service time TH = throughput %CPU = percent CPU

43 Design Phase Performance Factors Hardware Resources Memory Item Low High Delta XenApp Session 500 MB 1.2 GB 140% Database Session 10 MB 75 MB 650% Database Cache 200 MB 200 GB 99,900% SOC Process (Dynamic Map Service) SOC Process (Image Service) SOC Process (Geoprocessing Service) 50 MB 500 MB 900% 20 MB 1,024 MB 5,020% 100 MB 2,000 MB 1,900% SOM 30 MB 70 MB 133% Wide ranges of memory consumptions

44 Performance Factors - Hardware Virtualization Performance depends on configuration and implementation % Overburdened VMs will incur significant performance degradation

45 Capacity Planning Uncertainty of input information Planning hour Identify the Peak Planning Hour (most cases).

46 Capacity Planning Uncertainty of input information 100 High Active Users Uncertainty level Think Time Capacity Model Operation Details 0 Low Input information Hardware (SpecRate) Define user load first.

47 Capacity Planning Uncertainty of input information License Total employees Usage logs

48 Performance Factors - Hardware Network 1. Distance 2. Payload 3. Infrastructure

49 Performance Factors - Hardware Network Network accelerator improves performance of repeated request.

50 Performance Factors - Hardware Network transport time Required bandwidth - Response size - Number of transactions Mbps TH Mbits / req 3600 Network transport time Response size Effective bandwidth Transport(sec) Mbits / req Mbps Mbpsused All Built into System Designer

51 Network Testing Important for cloud based solutions Single data center = lower cost Performance depends on network: good bandwidth and low latency Cloud vendors offer multiple location. Which one is the best for your global solution? Esri UC2013. Technical Workshop.

52 Demo Network Speed Test Tool:

53 Performance Factors - Hardware Network

54 Performance Factors - Hardware Hardware Resources Network Impact of service and return type on network transport time - Compression - Content (e.g., Vector vs. Raster) - Return type (e.g., JPEG vs. PNG) Network Traffic Transport Time (sec) 56 kbps 1.54 Mbps 10 Mbps 45 Mbps 100 Mbps 1 Gbps Application Type Service/Op Content Return Type Mb/Tr ArcGIS Desktop Map Vector Citrix/ArcGIS Map Vectror+Image ICA Comp Citrix/ArcGIS Map Vector ICA Comp ArcGIS Server Map Vector PNG ArcGIS Server Image JPG ArcGIS Server Map Cache Vector PNG ArcGIS Server Map Cache Vector+Image JPG

55 Demo System Designer

56 Tuning: A reproducible test cases Esri UC2013. Technical Workshop.

57 Tuning methodology Profile each tier starting from the top Total Response Time (t1-t2) Browser t1 Web Server t2 Wait Time ArcGIS Server Usage Time ArcSOC Search & Retrieval Time ArcSDE/DBMS Esri UC2013. Technical Workshop.

58 Fiddler Fiddler measurement approximately 5.2 seconds Esri UC2013. Technical Workshop.

59 Mxdperfstat Esri UC2013. Technical Workshop.

60 DBMS Trace Esri UC2013. Technical Workshop.

61 Oracle Trace Compare elapsed time Elapsed time slightly changed due to different test runs Esri UC2013. Technical Workshop.

62 Oracle Execution plan Inefficient spatial index Esri UC2013. Technical Workshop.

63 Tuning: No-reproducible test cases Esri UC2013. Technical Workshop.

64 Analyze Web server Logs IIS log measurement seconds Esri UC2013. Technical Workshop.

65 ArcGIS Server logs Analyzing lots of entries might be challenging Esri UC2013. Technical Workshop.

66 Parse ArcGIS Server Logs AGS Log parser tool makes it easy logparser "SELECT top 10 time, target, elapsed, message from 'C:\Program Files (x86)\arcgis\server10.0\server\user\log\*.xml' order by elapsed desc" -i:com -iprogid:lpx.ags_log -e 1 -q Esri UC2013. Technical Workshop.

67 Monitoring

68 Demo System Monitor -Introduction Esri UC2013. Technical Workshop.

69 Trend Analysis System Metrics System Monitor tool Esri UC2013. Technical Workshop.

70 Trend Analysis ArcGIS Server statistics Esri UC2013. Technical Workshop.

71 Trend Analysis HTTP custom requests Esri UC2013. Technical Workshop.

72 Trend Analysis Geodatabase statistics Examples of versioned geodatabase stats Esri UC2013. Technical Workshop.

73 Performance Testing

74 Testing Objectives - Meet Service-Level Agreement (SLA) - Bottlenecks analysis - Capacity planning - Benchmarking different alternatives Esri UC2013. Technical Workshop.

75 Testing Tools Test Tools Open Source Pros LoadRunner No Industry Leader Automatic negative correlations identified with service-level agreements HTTP web testing Click and script Very good tools for testing SOA Test results stored in database Thick client testing Can be used for bottleneck analysis Cons High cost Test development in C programming language Test metrics difficult to manage and correlate Poor user community with few available examples Silk Performer No Good solution for testing Citrix Wizard-driven interface guides the user Can be used for bottleneck analysis Moderate to high cost Test metrics are poor. Test development uses proprietary language. Test metrics difficult to manage and correlate Poor user community with few available examples Visual Studio Test Team No Low to moderate cost Excellent test metric reporting Test scripting in C# or VB.NET Unit and web testing available Blog support with good examples Very good for bottleneck analysis No built-in support for AMF No thick-client options Moderate user community JMeter Yes Free Tool Provides only response times Poor user community with few available examples Esri UC2013. Technical Workshop.

76 Testing steps Validate environment Design test Validate results Esri UC2013. Technical Workshop.

77 Designing test Profile requests Prepare test data Define transactions and requests Bind test data to requests Define a load test Esri UC2013. Technical Workshop.

78 Test data Observe correlation rela between feature density and performance. Esri UC2013. Technical Workshop.

79 Demo System Test - Introduction

80 Analyze results Compare and correlate key measurements - Response Time Vs. Throughput - CPU, Network, Disk, and Memory on all tiers - Passed and Failed tests Validation - Lack of errors does not validate a test - Spot check request response content size Esri UC2013. Technical Workshop.

81 Analyze results Valid Expected CPU and Response time correlation Esri UC2013. Technical Workshop.

82 Analyze results Invalid Validation Example - Test failure memory bottleneck in w3wp process Esri UC2013. Technical Workshop.

83 Demo System Test load test

84 Throughput (Tr/sec) User load ASAKOWICZ1 Step Load Avg. Value Std. Deviation

85 Response Time (sec) Service Time ArcGIS Server Wait Time CPU ASAKOWICZ1 Step Load Avg. Value Std. Deviation Transaction Response ASAKOWICZ1 Step Load Avg. Value Std. Deviation

86

87 Demo System Test and Monitor: Editing

88 A table count Edit load test Compress 1 (ArcGIS Service running) Compress 2 (ArcGIS Service stopped)

89 Compress Compress 1 (ArcGIS Service running) Compress 2 (ArcGIS Service stopped)

90 States Compress 1 (ArcGIS Service running) Compress 2 (ArcGIS Service stopped)

91 Total users Viewers Editors Edit test

92 Capacity planning: using test results Esri UC2013. Technical Workshop.

93 Test Results as Input into Capacity Planning Throughput = 3.89 request/sec (14,004 request/hour) Response time = 0.25 seconds Average CPU Utilization = 20.8% Mb/request = 1.25 Mb Esri UC2013. Technical Workshop.

94 Test Results as Input into Capacity Planning Input from testing - #CPUs = 4 cores - %CPU = TH = 14,004 requests/hour - SPEC per Core of machine tested = 35 ST = (4*3600*20.8)/(14,004 *100) = sec - Note Service Time is very close to Average response time of 0.25 Esri UC2013. Technical Workshop. ST # CPU 3600 % CPU TH 100

95 Target values 1. Server SpecRate/core= User load=30,000 req/hr 3. Network=45 Mbps Esri UC2013. Technical Workshop.

96 Target values Target CPU cores calculation Input to Capacity Planning: Esri UC2013. Technical Workshop. - ST = Service Time =.2138 sec - TH = Throughput desired = 30,000 request/hour - %CPU = Max CPU Utilization = 80% - SpecRatePerCpuBase = 35 - SpecRatePerCpuTarget = 10.1 Output - #CPU required =( [.2138*30,000*100]/3600*80]) *[35/10.1] - #CPU required = 7.7 cores ~ 8 cores No need to calculate it manually, System Designer Tool does it for you:

97 Target values Target network calculation Input to Capacity Planning: - Mb/req= TH = 30,000 request/hour Mbps TH Mbits / req 3600 Output - Network bandwidth required = 30000x1.25/ =10.4 Mbps < 45 Mbps available - Transport=1.25/( )=0.036sec Transport(sec) Mbits / req Mbps Mbpsused Esri UC2013. Technical Workshop.

98 Sizing using System Designer Input: - Throughput= ST= Mb/tr= Hardware=80.9 Spec Esri UC2013. Technical Workshop.

99 T Sizing using System Designer Input - Hardware=80.9 Spec Esri UC2013. Technical Workshop.

100 Summary Performance Tuning Process Skills Tools Sizing (Hardware and Software) Performance Testing Esri UC2013. Technical Workshop.

101 Thank you Please fill out the session evaluation Session ID:1092 Offering ID: 748 Online Paper pick up and put in drop box Esri UC2013. Technical Workshop.