Implementing ArcGIS Blog - Page 3

Cached map services are a popular and recommended way to provide a fast performing presentation of static data. When map services are cached, the server draws the data at a set of map scale levels you define and saves the images. Then, as the server received requests for the map, it is much quicker (and requires less CPU resources) to retrieve the pre-created cached images than it is to dynamically draw the map again. This is the benefit of cached map services.

Generally speaking, cached map services can support simultaneous requests from many users. Such services can scale well. Despite this well known performance characteristic, it is still a common requirement to load test a cached map service to see first-hand how it behaves and scales on the hardware of a particular ArcGIS Enterprise deployment.

This Article contains a walk-through for load testing a cached map service with an Apache JMeter Test Plan. The examples use a public accessible dataset. Using datasets in Coordinate Systems other than WGS 1984 Web Mercator Auxiliary_Sphere (WKID: 3857) should work, but the generated test data will be based on a WKID of 3857.

Table Of Contents

• Why Test a Cached Map Service?
• Cached Map Service Testing Challenges
• How to Test a Cached Map Service?
  • The Natural Earth Dataset
  • Test Data Generation
    • The Generate Bounding Boxes (Precision) Tool
    • Visualizing the Generated Data in ArcGIS Pro
    • Visualizing the Generated Data in a Text Editor
• The Cached Map Service Test Plan
  • Components of the Test Plan
    • CSV Data Set Config
    • Levels Of Detail List Logic
    • GetMapTile Logic
    • Cache Tile Loop and Path Population
      • Loop Controller
      • Counter
      • JSR223 Sampler
      • HTTP Request
• The Thread Group Configuration
• Validating the Test Plan
  • Transactions
  • Requests
• Test Execution
• JMeter Report
  • Throughput Curve
  • Performance Curve
• Final Thoughts
  • Additional Items Worth Mentioning
  • Assumptions and Constraints

Network Analyst has always been in-demand capability of ArcGIS Enterprise as it provides popular problem solving analysis types such as Route, Service Area, Closest Facility and Origin-Destination Cost Matrix.

This Article contains a walk-through for load testing a route solver service (map-based service) with an Apache JMeter Test Plan. It uses a public accessible dataset in the examples for the data generation and test configuration process. However, the testing procedure should work when using any valid network dataset. This Article assumes you are familiar with Apache JMeter and some of the Test Plan strategies we have been using in other discussions.

Table Of Contents

• Network Analyst Route
• Load Testing a Network Analyst Route Service
• How to Test a Network Analyst Route Service?
  • Network Analyst ArcGIS Pro Tutorial Data
  • Test Data Generation
    • Making the Tools Available from ArcGIS Pro
    • Launch the Generate Data (Solve Route) Tool
    • The Generate Data (Solve Route) Tool Inputs
    • Spatially Visualize the Generated Points
• The Route Solver Test Plan
  • HTTP Request
  • The Thread Group Configuration
• Validating the Test Plan
  • Transactions
  • Requests
• Test Execution
• JMeter Report
  • Throughput Curve
  • Performance Curves
• Final Thoughts

One of the most popular functions for consuming resources from an ArcGIS Enterprise Site is through hosted feature services. Their data source is managed by ArcGIS, the scale very well and visualization is performed on the client.

This Article contains a walk-through for load testing a hosted feature layer service with an Apache JMeter Test Plan. It uses a public accessible dataset in the examples for the data generation and test configuration process. However, any source using a Projected Coordinate System of WGS 1984 Web Mercator Auxiliary_Sphere (WKID: 3857) should also work. The Article assumes you are familiar with Apache JMeter and some of the Test Plan strategies we have been using in other discussions.

Table Of Contents

• Why Test a Hosted Feature Service?
• Hosted Feature Service Testing Challenges
• How to Test a Hosted Feature Service? 
  • The USGS Motor Vehicle Use Roads Dataset 
  • Test Data Generation 
    • Making the Tools Available from ArcGIS Pro 
    • Select an Area of Interest 
    • Run the Generate Query Extents Tool 
    • Adjust the Inputs for the Generate Query Extents Tool 
    • Validating the Generated Test Data 
• The Hosted Feature Service Query Test Plan 
  • Components of the Test Plan 
    • Data Reader Logic 
    • Operation ID Selection Logic 
    • Operation Loop and Parameter Population 
    • HTTP Request 
• The Thread Group Configuration 
• Validating the Test Plan 
  • Transactions 
  • Requests 
• Test Execution 
• JMeter Report 
  • Throughput Curves 
  • Performance Curves 
• Final Thoughts 

If you have a multiple-machine Portal for ArcGIS or ArcGIS Server site, you have a dependency on a file share.  If you are having a problem with your site, how do know whether the file share might be causing it?  This article is intended to help with that challenge.

The load testing of ArcGIS Enterprise can be carried out using a variety of different tools like: JMeter, LoadRunner or Silk Performer. While all test tools essentially perform the same task of applying pressure to a particular resource and measuring its impact, having a listing of the meanings to common phrases can help ensure testers and analysts are on the same page.

This resource provides insight into some testing fundamentals that are mentioned in other Community Articles about performance and load testing of ArcGIS Enterprise. The vocabulary definitions are listed from a chronological point of view. It all starts with a request so this is the first item discussed.

We are excited to offer Data Health Check appointments at this year's User Conference.  It's been a popular offering at UC for the past 10 years.  Users get to meet with an Esri industry expert, who will assess the quality of their GIS data (geometry and attributes) for use cases such as getting ready to migrate to the Utility Network or Parcel Fabric, connectivity issues in their geometric network, report/submit data quality, understand inherited data, readiness to migrate to indoors data model, and more.

Customers with water, wastewater, stormwater, electric, gas, linear referenced pipelines, addressing, land records, street centerlines, airports (airfield operations), and Indoors datasets can sign up for a free, 45-min virtual appointment. 

Learn more about this awesome offering here.

If you are ready to sign-up, click here.

As the foundational software system for GIS, ArcGIS Enterprise performs many duties such mapping and visualization, analytics. If one function were to be used as a benchmark for testing an ArcGIS Enterprise deployment, a strong case can be made for the map service export function. Export map can be called easily in an Apache JMeter Test Plan by varying the spatial extents of the requests across several map scales.

This Article provides a discussion on the key components of running such a benchmark like the dataset, service instances and step load. For comparison purposes, results are also listed of the benchmark performed within an Esri test environment.

Table Of Contents

• Choosing a Capability of ArcGIS Enterprise to Benchmark
• What is a Benchmark of a Map Service?
• Benchmark Dataset
  • What is Public Domain Data?
  • Why Use Public Domain Data?
  • SampleWorldCities vs Natural Earth
    • The Benchmark Natural Earth Dataset
  • Deployment Architecture
  • Data Source Type and Location
  • Service Type and Number of Instances
  • Do the Request Options in a Benchmark Test Matter?
• The Map Service Benchmark Test Plan
  • The Thread Group Configuration
• Benchmark Test Execution
• Results and Analysis
  • The Ideal Throughput Curve
  • The Ideal Performance Curve
• JMeter Report
  • Actual Throughput Curve
  • Actual Performance Curve
• Comparing the Results

Performance Engineering: Load Testing ArcGIS Enterprise

Performance Engineering is the practice of proactively testing, monitoring and analyzing an ArcGIS Enterprise deployment or application from the perspective of performance and/or scalability. System performance and scalability are critical factors in the successful adoption, operation, and long-term use of an ArcGIS Enterprise deployment.  They are often key determinants of end-user satisfaction.

From this post can link you to all of our Articles related to strategies and practices with Load Testing ArcGIS Enterprise.

Apache JMeter is an open source Java software program for performance and scalability load testing. It is a free tool with GUI and command-line support for Windows, Linux and MacOSX that has many enterprise-level features.

This Article contains a walk-through for taking a SampleWorldCities map service Test Plan (created from previous a Article) and discussing how it can be extended to support ArcGIS Enterprise Authentication. It assumes you are familiar with Apache JMeter and some of the Test Plan strategies we have been using in other Articles. For a refresher, please see: 

• Performance Testing with Apache JMeter (An Introduction)
• Creating a Load Test in Apache JMeter against the SampleWorldCites Map Service (Beginner/Intermediat...
• Running an Apache JMeter Load Test from Command-line mode (Beginner/Intermediate)

Table Of Contents

• Why Add Authentication to a Test Plan?
• Getting Started
• Creating the sampleworldcities4 Test Plan
• Extending the Test Plan to Add Authentication Support
  • User Defined Variables
  • Authentication Requests to Acquire a Token
    • OAuthState HTTP Request
    • OAuthState Regular Expression Extractor
    • AccessToken HTTP Request
    • AccessToken Regular Expression Extractor
    • Token HTTP Request
    • Token Regular Expression Extractor
    • Token Response Assertion
  • Token Support in the Map Request Headers
• Validating the Test Plan