#9011 GeoMedia WebMap Performance Analysis and Tuning (a quick guide to improving system performance) Messina Thursday, 1:30 PM - 2:15 PM Paul F. Deaver, Sr. Consultant Security, Government & Infrastructure Intergraph Corporation, Huntsville, AL Paul.Deaver@intergraph.com
Abstract As the demand for geospatial data grows, system administrators face increasing requirements for system performance. In this session, the presenter will address two aspects of performance: IT hardware, software, and application architecture as it applies to GeoMedia WebMap, and analysis of GeoMedia WebMap applications to identify and resolve performance bottlenecks. October 7, 2008 2
Anatomy of a Web Request Web Request Internet Firewall DMZ Switch Firewall Switch Users WebMap Server(s) Database Server(s) Internet Users Web Content Database Content October 7, 2008 3
Anatomy of a Web Request #1 Insufficient Network Bandwidth Internet Firewall DMZ Switch Firewall Switch Users WebMap Server(s) Database Server(s) Internet Users Web Content Database Content October 7, 2008 4
Anatomy of a Web Request Internet Firewall DMZ Switch Firewall Switch Users WebMap Server(s) Database Server(s) Internet Users Web Content Database Content #2 Inadequate Web Server October 7, 2008 5
Anatomy of a Web Request Internet Firewall DMZ Switch Firewall Switch Users WebMap Server(s) Database Server(s) Internet Users Web Content Database Content #3 Inadequate Database Server October 7, 2008 6
Anatomy of a Web Request Internet Firewall DMZ Switch Firewall Switch Users WebMap Server(s) Database Server(s) Internet Users Web Content Database Content #4 Poorly Designed Database October 7, 2008 7
Anatomy of a Web Request Internet Firewall DMZ Switch Firewall Switch Users WebMap Server(s) Database Server(s) Internet Users Web Content #5 Poorly Designed Web App. Database Content October 7, 2008 8
Anatomy of a Web Request Internet Firewall DMZ Switch Firewall Switch Users WebMap Server(s) Database Server(s) Internet Users #6 Undersized Client Hardware Web Content Database Content October 7, 2008 9
Performance Audit Methodology A Good Technology Audit Requires Current user experience Web server hardware size, capabilities, software, and configuration Database server size, capabilities, software and configuration Network configuration and bandwidth Database configuration / tuning Data contents, format, indexing, metadata, use Web application design / review 1, 2, and 3-year outlook for the system Performance Testing (baseline) October 7, 2008 10
Current User Experience What are user opinions on Application performance? Application stability? Does the Web application do what you require? Other comments? How do users use the system What are your typical workflows? What other [unintended] uses have users found for the system? How is the system currently loaded How many and what types of users rely on this system? Typically, many of maps per day are generated? Under peak load, how many maps per day are generated? October 7, 2008 11
Web / Database Server Analysis Before you begin, document your hardware infrastructure What are your CPU s design feature? Manufacturer (Intel / AMD), speed, number or chips, number of processing cores How much physical memory is installed? Memory speed, bus speed, etc. How much disk is installed? Total storage, file system type, disk controller type & manufacture, etc. What OS and add-on software is installed? Software versions, memory and CPU requirements, etc. What are the current system maintenance procedures? OS and application patches procedures Logs and audit trails Backups Regularly scheduled log / audit / backup review October 7, 2008 12
Web / Database Server Analysis Typical Server configuration problems Insufficient CPU Insufficient Memory Insufficient Disk I/O bandwidth Insufficient Network bandwidth Poorly maintained server Poorly designed database Poorly designed Web application Severe security holes October 7, 2008 13
Web / Database Server Analysis Analysis Tools Windows Task Manager A simple tool to be avoided!!! Windows Process Monitor Provides sampled metrics Analyze process memory, CPU load, file handles, disk I/O, network I/O Analyze IIS operational efficiency Analyze Database operational efficiency Analyze GeoMedia WebMap operational efficiency Other Windows Administrator Tools Event Viewer Analyze logs regularly. You will find issue to resolve. Analyze / resolve disk fragmentation (but never defragment an active database) SysInternals Tools Best-in-class tools for the Windows IT analyst Analyze detailed system configuration Analyze detailed CPU, memory, handle, I/O Analyze detailed disk and file I/O overhead Analyze detailed registry I/O overhead http://www.sysinternals.com/ October 7, 2008 14
Network Bandwidth Analysis Before you begin, document your network infrastructure How are the servers connected to each other? How are the servers connected to end users? What switches / firewalls / routers are involved? What are the documented bandwidth capabilities at each connection point? What Web application traffic uses these networks? What other network traffic uses theses networks? October 7, 2008 15
Network Bandwidth Analysis Typical Internet problems Insufficient switching Insufficient bandwidth for Web data Insufficient firewall bandwidth Poorly designed Web application Severe security holes Typical problems Insufficient switching Insufficient bandwidth for spatial data Insufficient firewall bandwidth Poorly design database Common to Internet & Insufficient Web and/or Database server network bandwidth Poorly designed Web application October 7, 2008 16
Network Bandwidth Analysis Analysis Tools Switches and Firewalls often include diagnostics to report on device performance. Please consult your network hardware documentation. When no internal diagnostics are available, it may be necessary to put a network sniffer device on critical points in your network to identify actual load. Web and database server I/O can be monitored using Windows built-in Network Monitor Driver. Another favorite analysis tool is Wire Shark. Pay attention to the amount of data sent to/from Web users vs. to/from the spatial database. High data volumes can be the result of a heavy load, a poorly designed Web application, or poorly designed database. October 7, 2008 17
Database Application Analysis Before you begin, document your database application Database (Oracle / SQL*Server) configuration and tuning Memory allocation CPU allocation Other database initialization parameters October 7, 2008 18
Database Application Analysis Typical Data problems The database engine is not tuned for the hardware on which it s installed The database server hardware is undersized for the intended application load The database server is poorly maintained The selected database engine is not suitable for the applications that use it Severe security holes October 7, 2008 19
Database Application Analysis Is your selected database engine suitable for the data you serve? Database Suitability Matrix Access Software Cost 4 5 5 2 1 1-Expensive Software Maintenance 4 5 4 2 1 1-Expensive General data query performance 3 1 1 5 5 1-Slow Spatial data query performance 3 1 5 4 5 1-Slow Scalable 1 1 1 4 5 1-Not Scalable Ease to maintain 5 5 4 3 1 1-Difficult Technical Size Limitation 2GB 2GB 2GB - - Practical Size Limitation 100MB 100MB 2GB - - Read/Write Yes No No Yes Yes Read/Write with Transacations No No No Yes* Yes Enterprise data store No No No Yes Yes Industry-recognized No No No Yes Yes Long-term Cost Low Low Low Medium High ArcView SmartStore SQL*Server Oracle October 7, 2008 20
Data / Database Analysis Before you begin, document your data characteristics Data formats (Oracle, SQL*Server, Access, ArcView, MapInfo, etc.) Database tables and/or map layers in each of these formats Coordinate standards (map projection) Size, density, digitized accuracy Volatility (how often it changes) Standards / relationships / reliability / consistency Atypical uses (e.g., other than map display & click to query) How it s queried How it s indexed October 7, 2008 21
Data / Database Analysis Typical Combined Data / Database problems Insufficient CPU Insufficient Memory Insufficient Disk I/O bandwidth Insufficient Network Bandwidth Poorly tuned database instance Inconsistent data Corrupted data Data that s not suitable for use by the application Poorly implemented spatial / attribute data Poorly indexed data SQL query / database indexing mismatch October 7, 2008 22
Data / Database Analysis Typical Database problems Insufficient CPU Insufficient Memory (swapping causes Disk I/O) Insufficient Disk I/O bandwidth (the slowest hardware within a computer) Insufficient Network Bandwidth (typically the slowest I/O pathway) Poorly tuned database instance (too little/much RAM causes disk I/O) Poorly implemented spatial / attribute data (bad designs require more query) Poorly indexed data SQL query / database indexing mismatch (un-indexed queries cause excessive disk scanning i.e., I/O) A Comment on Solid State Disk Drives Example (first hit from Google): http://www.storagesearch.com/ssd-buyers-guide.html October 7, 2008 23
Data / Database Analysis Before analyzing your database for efficiency #1 Analyze your Hardware CPU Type, Speed, Cache Internal Bus Speed RAM Quantity and Speed Disk I/O Channel (controller type) Disk RPM Network I/O #2 If possible, replace hardware that is obviously deficient #3 Tune the database engine to suit the hardware on which it is installed #4 Analyze typical use to identify how the data is used October 7, 2008 24
Data / Database Analysis #5 Create and implement a consistent indexing strategy Do Index tables that are frequently queried for less than 2% to 4% of the table s rows Index all tables with more than 100-200 records Index key columns such as ID, MSLINK, etc., when indexing is required Index frequently queried database columns Index database columns that join to other tables either by query or by view Index uniquely where possible Spatially index Oracle geometry Do Not Index every column in a table unless you have query criteria for every column Index a table before loading or translating a large quantity of data into it Index a table when others are using the database October 7, 2008 25
Data / Database Analysis Now it s time to analyze your databases Analysis Tools Oracle Database Analysis Tools Enterprise Management Console performance tab STATSPACK / AWR analysis packages SQL*Server Database Analysis Tools Database Engine Tuning Advisor SQL Server Profiler Common Analysis Tools Windows Performance Monitor SysInternals Tools A good 3 rd party DBA to peer review your database implementation October 7, 2008 26
Web Application Analysis Before you begin, document your Web application What data sources are added to each map? At what map scale? Are you using a Publisher or home-grown application? If home-grown Who is the developer? What are the developer s experiences? What language was used to write the Web application? What special capabilities were written into this Web application? What 3rd party applications or objects have been integrated into the application? Were best practices coding practices followed for the language that was selected for this site? Was the Web application designed to take advantage of optimizations related to the selected database? Was the Web application designed to target a collection of Web client users? Which users? Win95? AOL? FireFox? Opera? October 7, 2008 27
Web Application Analysis Typical Web application problems WebPub Inappropriate map content for a given map scale Typical Web application problems Home-grown A good developer deploys a Desktop application with no consideration for multi-user Web issues Inappropriate map content for a given map scale Bad database query / indexing strategy Dirty Web code doesn t handle a full range of data Failure to cache Web content Failure to consider the range of client hardware that will use the Web site Failure to test for and support client plug-ins: JavaScript, Java, CGM / Adobe Plug-ins, FireFox eccentricities Severe security holes October 7, 2008 28
Web Application Analysis Tools Windows Performance monitor (IIS, WebMap) IIS Log review (Manually or using WebLog, AnaLog, or other analysis tools) WebMap GWMLog review (detailed timing characteristics for every map query) SysInternals system analysis tools A good 3 rd party developer to peer review home-grown code October 7, 2008 29
Web Application Futures Do the applications meet user performance and availability requirements today? Never, Sometimes, Usually, Always What is your vision for the system? 1 year, 2 years, 3 years How will the data change? Size, Complexity, New data, Integration with other data Have you performed capacity planning and analysis testing? Database server testing, Web server testing, etc. October 7, 2008 30
Tuning Once the audit is complete Using all available instrumentation, allow a user perform end-to-end use of the system, collecting metrics. This is the baseline by which all optimizations will be measured. Document metrics, identifying the best opportunities for improvement Make improvements, 1 at a time, testing afterwards to quantify the quality of the change. Perform a final baseline analysis, identifying system bottlenecks. Document new user perceptions of the system. October 7, 2008 31