Architecting ArcGIS Server Solutions for Linux and Solaris

Transcription

1 Architecting ArcGIS Server Solutions for Linux and Solaris David Cordes Cherry Lin Egor Podgornov ESRI Developer Summit

2 Schedule 75 minute session minute lecture made up of moments of horror (demos) interspersed among checking your blackberry (slides) minutes Q & A following the lecture demos/blackberry Cell phones and pagers Please complete the session survey we take your feedback very seriously!

3 Introductions Who are we? Product Engineers Members of ArcGIS Server dev team. Willing to do anything to get to go to Palm Springs Who are you? Implementers / Architects GIS Administrators GIS Decision Makers Consultants Generous and kind people who will give high marks on their evaluations

4 Goals Solve real world AGS architecture problem Achieve performance, stability, uptime Show you, not tell you Keep you interested enough that you don t t leave at 5:15 to get dinner.

5 Real-world Scenario Serve city maps and provide driving directions X peak map 0.75s/request Y peak z analysis 2s/request ESRI Developer Summit

6 Approach Reality check Publish map and model Generate map cache Validate Size Hardware Setup Configuration Ask for Raise ESRI Developer Summit

7 Publishing Map & Model Authored on Windows, moved to Linux Mxd Path Editor Publish with Manager Check your blackberry your coworkers are having a crisis. ESRI Developer Summit

8 Publishing Map & Model Demo Mxd Path Editor Manager Acting as if nothing has gone wrong ESRI Developer Summit

9 Approach Reality check Publish map and model Generate map cache Validate Size Hardware Setup Configuration ESRI Developer Summit

10 Generate Map Cache Cache = fast Requires planning Don t t generate in production Use NAS Use the script ESRI Developer Summit

11 Generate Cache Demo The generate map cache script Typos ESRI Developer Summit

12 Approach Reality check Publish map and model Generate map cache Validate Size Hardware Setup Configuration ESRI Developer Summit

13 Validate Performance Goals Are performance goals achievable? Request time = SOC + network + browser Dynamic maps: 80/15/5 rule Cache = 0 SOC time, multiple tiles GP: SOC more than 80% SOC time ESRI Developer Summit

14 Validate Performance Demo Stop Watch for map performance REST + JMeter for GP performance Talking while clicking ESRI Developer Summit

15 Approach Reality check Publish map and model Generate map cache Validate Size Hardware Setup Configuration ESRI Developer Summit

16 Hardware Sizing 1. Load test single machine 2. Find max load for machine 3. # machines = required load / single machine max SOC load only ESRI Developer Summit

17 Hardware Sizing Demo Demo Use JMeter to load test Find max load for machine ESRI Developer Summit

18 Approach Reality check Publish map and model Generate map cache Validate Size Hardware Setup Configuration ESRI Developer Summit

19 Configuration Setup Need 3 SOC machines No single point of failure Two SOMs Both SOMs work with 3 SOCs Diagram Goes Here ESRI Developer Summit

20 Configuration Setup Demo Install Demo Machine 2 perform silent install of SOM + SOC Machine 3 pre-installed with SOC but not configured Diagram Goes Here ESRI Developer Summit

21 Configuration Setup SOC machines can take orders from two SOMs Requires step Diagram Goes Here ESRI Developer Summit

22 Configuration Setup Demo Install Demo Machine 2 perform silent install of SOM + SOC Machine 3 pre-installed with SOC but not configured Diagram Goes Here ESRI Developer Summit

23 Recommended Sessions Implementing and Optimizing Cache Tuesday 4:30 in Catalina/Madera Thursday 10:15 in Primrose A Architecting for Performance Wednesday 10:30 in Primrose B Wednesday 2:45 in Pasadena/Sierra/Ventura Architecting for Linux/Solaris Wednesday 4:30 in Catalina/Madera Implementing Security for.net Wednesday 2:45 in Primrose B Thursday 1:30 in Smoketree A-E Implementing Security for Java Thursday 10:15 in Pasadena/Sierra/Ventura

24 Bonus Material JMeter The following bonus slides show how to setup the JMeter test plan I used in the demonstration. JMeter is a free tool, it s not easy to use, but pretty powerful. A similar style test plan could be used to calculate how long dynamic map requests take using a REST url. (note: REST is new to ArcGIS Server 9.3) I also used a JMeter test plan to get performance numbers for a geoprocessing operation using its REST url. That test plan requires a lot of advanced knowledge about REST and JMeter and so I have not covered it. It s a possible topic for a future presentation.

25 Bonus Material JMeter Http Request Defaults This is the Http Request Defaults page. I set web server and port here for all requests.

26 Bonus Material JMeter Cache Thread Group The thread group is where I set the number of simultaneous users.

27 Bonus Material JMeter Cache URLs I define the URLs I want to hit as variables here. I determined URLs by browsing cache virtual directory. Each variable starts with cacheurl followd by an underscore (_) and then a number.

28 Bonus Material JMeter For Each Controller When test plan is run it will look for variables with the format cacheurl_<number>. For each variable it will do the GetCache http request and HTTP 200 validation because they are children of this controller. Each time it repeats these steps it changes the url variable to have a different value based on the current cacheurl_<number> variable.

29 Bonus Material JMeter The GetCache Http Request I leave web server and port number blank for the request because I want it to use the default values. I set the path to ${url} which means it should get the value from the url variable.

30 Bonus Material JMeter The Http 200 Assertion I added a response assertion that checks the response code whether it contains the value 200. An HTTP response of 200 means success. Anything else is considered a failure. In the left panel this is after the GetCache Http Request and so it gets executed after the request is complete.

31 Bonus Material JMeter Summary Report I added a Listener called Summary Report which tells you how many tests were run and how many were successful and time values (in milliseconds). In this case I only have the GetCache http request and the average is 11 milliseconds.

32 Bonus Material JMeter Summary Report I added a Listener called Summary Report which tells you how many tests were run and how many were successful and time values (in milliseconds). In this case I only have the GetCache http request and the average is 11 milliseconds.