分布式部署与性能优化

分布式部署•ArcGIS Server应用部署中总共有这个几个部分：WebServer，SOM，SOC，DataServer•单层结构•双层结构•三层结构具体部署中注意的问题•SOM和SOC机器上的用户名和密码相同•Mxd以及数据源所在目录的权限•输出图片的目录的权限•发布服务时候的参数要使用UNC目录性能优化ArcGIS Server: Response time factorsBrowser

•Four main factors of response time•Multiple tiers•Performance Transmission

Time

Web Server

Wait Time

SOM

bottleneck can occur in each tierUsage Time

SOC

Search & Retrieval Time

SDE

ArcSDE

数据方面•数据量对数据进行分析，在可能的情况下，对数据进行一些简化操作•数据组织角度属性字段索引，空间索引大小的调整Mxd数据的组织（对动态服务而言）•较少数据图层•图层按比例控制•使用annotation来代替label•减少复杂符号Best PracticesGeneral Guidelines•Show relevant information–Start simple (additional layers can be toggled on by user)–Use field visibility (hide unnecessary attributes)•Use scale dependencies –Use data appropriate for the given scale (generalize if necessary)–Display similar number of features at all scales for consistent user experienceBest PracticesPoint, Line & Polygon rendering For non-cached, dynamic layers•Points–Use single layer Simple or Character markers for best performance–Use EMF instead of bitmaps–Use Integer (vs. character) fields for symbol values–Avoid halos, complex shapes, masking•Line & Polygons–Use ESRI_Optimized style–Avoid cartographic lines (also includes polygon outline!)ESRI_Optimized•For lines & polygons•Outlines for all fills are simple lines instead of cartographic lines•Picture fills are emf-based instead of bmp-based•Improves drawing performance by > 50%Best PracticesText and labeling•Use annotation instead of labels•Use indexed fields (reduce label SQL query number and complexity when possible)•Use label and feature conflict weights sparingly•Avoid special effects (fill patterns, halos, callouts, backgrounds)•Avoid very large text size (60+ pts)•Avoid Maplex for dynamic labeling•Avoid overuseSymbolizing data effectively: Labels / Text••••••

Use larger size Use wider line and character spacingUse sans serif, open-letter fontsMinimize special effects (e.g. italics)Minimize text backgrounds (e.g. callout boxes)Don’t overuse Labels–ID tool can be used–Use scale dependency 服务的组织•不要把所有的图层都放在一个服务中，图层很多的情况下可以分放在不同的服务中，这样可以使用多进程来完成所需请求，从而提高相应速度服务的设置（一）•池化的服务性能会超过非池化，因此在功能许可的情况下，尽可能使用池化服务•在使用编辑等一定要使用非池化的服务的情况下，要尽可能的把非池化的服务中的图层减少，而把他们增加到池化服务中服务的设置（二）•使用MapCache，这是一个非常有效的提高客户端的用户感受的方法•在创建cache的时候，如果第一次出现错误，可以使用updatecache来进行弥补瓶颈•CPU•MemoryCpu瓶颈：动态服务的池化实例的最优个数•Set instances to level where maximum throughput occurs (usually between 2 to 4 instances per CPU)CPU bottleneckThroughput (maps/hour)Nnumber of instancesMemory 瓶颈Memory Bottleneck –Solutions••

Increase physical memoryLimit capacity on host machinesSetting Capacity •Limits number of service instances running on a specific host machine. •Once this limit is reached, Server starts replacing least recently used instances instead of creating new ones.•Serve large number of services only part of which are used at any point in time–Usage sliding from European to U.S. map services over time.–Supports “limited resource” scenario•Serving a large library of maps•Individual services rarely usedBuilding Map Service Cache•Renders 4K x 4K images–1 GB consumed by just 3 processes•Options to resolve–Increase memory to 2 or 3 GB–Reduce number of instances per serverMemory and CPU usage by Service Type–Dynamic map service•CPU Usage = High•Memory = Low*–Static Map and Globe services•CPU Usage = Low•Memory = Low–Editing map service•CPU Usage = High•Memory = High•Database connections = High–Geoprocessing service•CPU = High•Memory = High•I/O = HighDetecting Bottlenecks•Single user testing is inadequate•Simulating multiple users–Low Tech: •Recruit others in the office and synchronize over the phone–High Tech: Load simulation tool Load Simulation Tool•Build–Code your own test harness•Buy–Price: (free/bundled to $100K or more)–Technical vs. Functional–Microsoft•Web Application Stress Tool (WAST)•Application Center Test (ACT)•Visual Studio 2005 Team Edition for TestersMeasuring Web PerformanceClient Response TimeHow “fast” does web application appear to remote browser hitting the site–Response Time (average, 75thpercentile, max)–

•

•

Machine ThroughputMeasured in requests/sec–Determines number of servers you need to buy–

Visual Studio 2005 Team System•Tester tools are now on par with Developer Tools•Unit, Web, Load, and Manual tests•Measures code coverage VS 2005 –Recording a Web Test•A series of HTTP URLs that can be created or recorded from a browser session.VS 2005 –Creating a Load TestVS 2005 –Running a Load TestMonitor Statistics and Log Files•Creation Time•Wait Time•Usage TimeLog File Behavior•Modify Log Level in Server.cfg–0 (None): No logging–1 (Error): Serious problems –2 (Warning): Additional errors.–3 (Normal): Common administrative messages of the server, warnings, and errors are logged.–4 (Detailed): Common messages from user use of the server, including server objects, normal messages, warnings, and errors are logged.–5 (Debug): Verbose messages to aid in troubleshootingQuestions?High Availability Configuration