1. Welcome EUC11

2. Enterprise GIS: System ArchitectureDesignIsaac MedelFrancesc Puigvert Esri Spain 3. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 4. System Architecture DesignUser needs Infrastructure specifications Data resources Network designHardware People(information products)Applications 5. PlannningIdentify business requirements User Workflows / Services Peak system design loads Data center hardware specifications Network infrastructure needsDefine project requirements Project budget Project schedule System performance needs Return on investment/fundingReduce Implementation Risk Identify key performance parameters Establish system performance targets Define system performance validation plan 6. Why is System Architecture Design Important?Reduce cost Improve productivity Balanced system designServers NetworkDBMS GeodatabaseStorage ClientsArcSDE ApplicationHardware infrastructureDatabase designUser workflow System architecture design Framework for productive operations 7. Stages Support a successful implementationApplication developmentPrototypetestData Construction needsDesignSystem designImplementationRequirementsSystemdelivery Building a GIS User needsis an Incremental Process 8. Capacity Planning Tool: System Design Design tabUser workflow requirements Network Display suitability performancePlatform Selection Platform sizing and utilization 9. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 10. GIS Software EvolutionWhat are the lessons learned?Platform Performance Change >> 10x Faster Hardware >> 10x Faster Hardware >> 10x Faster Hardware > 2x Process Load> 2x Process Load>> 10x Faster Technology Change>> 10x Faster Technology Change Service Oriented ArchitectureTightly Scripted Software CodeObject Relational Software Hardware Virtualization ArcGIS Server AMI19821999Cloud Computing GIS iPhone AppsArcGIS Desktop ArcGIS 2008 -2009 ArcGIS 2010 ARC/INFO 1982- ArcInfo 1999 - REST API-ArcGIS.com- ArcEditor 2000 - WEB 2.0 Interoperability-Online Community BasemapArcView GIS 1992- ArcView- User Publishing / Collaboration -Intelligent Maps, Web Mapping MapObjects 1996 - ArcGIS Server 2004- ArcGIS Online Resources -Packaging toolset (layers, maps) - Rich Internet Clients -Mosaic Dataset, Image ProcessingArcIMS 1997- ArcGIS Engine - Javascript, Flex API, Silverlight Javascript, -Crowd ComputingCoveragesArcSDE 1999ArcGIS Server 2009 New search toolsLibrarian- Geodatabase Versioning -Faster Maps New parcel fabric Shapefiles(ArcSDE) -Map Cache Temporal Analysis - Distributed Geodatabase-Map Service Description (MSD) ArcStorm -Optimized Mapping tools ReplicationSpatial Database Engine (SDE)- Simple non-versioned file types non-ScriptsObjectsServices 11. GIS Is Deployed in Many WaysDepartmental EnterpriseTraditionalEmerging 12. Esri Product Family Desktop GIS ArcInfoArcGIS ExtensionsArcEditorMobile GISArcViewGIS Web ServicesArcPad ArcReaderArcGIS.com ArcGIS MobileOnline Resource Centers ArcGIS EngineTemplates, Forums, CollaborationGlobal Map Cache, Community Basemap, 3D Viewers Intelligent maps, Web mappingGoogleVirtual Earth ArcGISExplorer Lightweight NetworkDeveloper GIS ViewersESRI Developer Network(EDN)Web BrowsersXML/SOAP/OGCREST (Javascript, FLASH, Silverlight)Server GIS ArcGIS ServerArcSDE Image Server ArcIMSBlending into a single server product line GIS DataFilesGeodatabase ImageryMap CacheDistributed Geodatabase Management 13. Desktop OperationsStand alone DesktopConnected DesktopCentralized Desktop Management ICARDPArcGIS DesktopArcGIS DesktopDirect Connect* SDE CitrixMicrosoft Personal ArcSDEDBMS Client Windows Terminal Server ArcGIS DesktopFile GDBMap CacheDirect Connect* SDEArcGISDBMS ClientServer ArcGIS.com World Basemaps Map Cache Community Basemaps GeodatabaseFiles ImageryMap Cache Web Maps and Services Physical or Virtual Servers 14. Esri Mobile OperationsStand alone Desktop ArcGIS MobileArcGIS Desktop ArcPad(smart clients)Protected Data Cache Personal ArcSDE4 or 10 GB SDE GDB DataSynchronization ExchangeFile GDB Map Cache 1 TB Geodatabase iPhoneReplicationapplicationWeb ServerWeb Services ArcGIS.comArcGIS Server World Basemaps Map Cache Community Basemaps Web Maps and ServicesFiles GeodatabaseImageryMap CachePhysical or Virtual Servers 15. ArcGIS Server Web Operations Google Microsoft HTML Browser ArcGIS Desktop ArcGIS ExplorerADF Client 3D Analyst Online ArcGIS DesktopArcGIS ExplorerWeb Maps HTML Browser ArcGIS EngineJavaScript 2D and 3D ServicesData Services Rich Browser ClientsGeoprocessing ServicesFlash / SilverlightAmazon Cloud ArcGIS iPhone / Android (soon) ServerEnterprise Data Center ArcGIS.com.NET/JAVA WAS SOAPRESTOpenApp Dev Framework StandardsArcGIS ServerWorld BasemapsMap CacheCommunity BasemapsWeb Maps and Services Files GeodatabaseImageryMap CachePhysical or Virtual Servers 16. Software Technology SelectionGIS Data SourceRemote Data SourcesAmazon CloudInternal Data Sources ArcGIS ServerFiles GeodatabaseImageryMap Cache Internet ServicePhysical or Virtual Servers WTS(Citrix)Network Services LAN Web ServerPublished Network Services ArcIMS ArcGIS Distributed Batch ProcessingServerWeb ServicesPublished Map ProductsWorkstationsPublished Geoprocessing ServicesBrowserWANWeb Editing / Crowd ComputingDesktop ApplicationsIntegrated Business WorkflowsProfessional GIS UsersDatabase MaintenanceHeavy Business WorkflowsGIS Project EffortsData ConversionTerminals BrowserMobile ApplicationsDisconnected OperationsLoosely Connected Workflows 17. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 18. Geodatabase Geographic Data Store - Scalable, multi-user Core ArcGIS Data modelNetworksSurvey AddressesVectorsAnnotations Transactional model for 3D ObjectsAttributes GIS workflows DimensionsTopology COM Components forTerrain Parcels data accesibility Cartography CADRaster 19. Data management approach Geodatabase built on a table structure- Spatial Data Types & SQL- Relational Integrity- Scalability, Reliability, Flexibility- Support for continous, large datasets Based on the simple feature model- Points, Lines, Polygons- Open Access 20. Complex behavior in the Geodatabase Validation Rules- Attribute, connectivity andrelationships Domains- Ranged or coded values Subtypes- Defined as the class level Relationship classes- Association between objectson different classes 21. Complex behavior in the Geodatabase Geometric Networks- Connectivity rules Network datasets- Multi-modal networks- Turns, restrictions, costs Topology- Set of rules that define spatial behavior- Ensure data integrity Parcel fabrics 22. Versioning Technology that allows multiple users to edit andview data at the same time- Appears to users as if they have their own copy of atable- Does not apply locks or duplicate data DefaultReadersVersion1Version2Editor 1 Editor 2 23. ReplicasArcSDE GDBGeodatabase replication extendsDFLT the concept of versioning toParent VR1 VR2 multiple databases.Childcheck out check inDFLTArcSDE GDB V1V2File GDBDFLT ParentChildArcSDE GDBVR1VR2TwoOnewayway- Versions in parent and child geodatabases are used as replica versions.File GDBDFLT DFLT - Changes in this replica versions are transferred during synchronization V1V2ArcSDE GDBArcSDE GDB 24. Replication types Checkout/Check-in replication: One time - Edits in child replica can be syncronized one single time Parent Child with parent replica. SDE - Uses: Disconected editing; File GDB as a requisite.SDE PGDBFGDB One-way Replication: - Allows data changes to be sent multiple times in a single DevelopmentProduction direction (parent-to-child or child-to-parent) - Data in origin GDB are editable; data in destination GDB arePersist read-only. EditRead - Changes in destination GDB are overwritten during SDE (child-to-parent) syncronization if edits in origin GDB exist. SDEPGDB - Uses: development-staging-production models; data FGDB publishing Two-way replication:Office AOffice B - Allows data changes to be sent multiple times, both ways. Persist - If the same row is edited in both replica geodatabases, it isEdit A Edit B detected as a conflict when the replicas are syncronized.SDESDEConflict resolution 25. Historical versions Geodatabase archiving.- Built on Geodatabase versions.- Enables recording and accessing changes made to a subset ofdata.- No need for storing snapshots for the entire database.- Archiving lives as long as the Version is alive.- Introduces a historical version.- Creation of historical markers possible. 26. Geodatabase compress Maintain database performance and health. - Delete all states that do not participate within a versions lineage. - Collapse any candidate lineage of states into one state. - Move rows from the delta tables into the business tables. BeforeAfter00 v2 v2 v1 DEFAULTv1v4 v4 DEFAULT 27. Geodatabase administration in 10.1 New Geodatabase administration dialog box- Manage versions- View and remove connections- View and manage locks- Block new connections For system tables:- Rebuild indexes- Update statistics 28. Managing data in ArcGIS 10.1 View and manage privileges View locks on a versionor specific dataset Rebuild indexes on multiple datasets Update database statisticson multiple datasets Enable editor tracking One-click spatial table registering 29. Enterprise Geodata ManagementProviding options for distributing geodata management activitiesGeodatabase VersionsDirect editingBasis for replication ProductionPublicationGeodatabase GeodatabaseConnected ReplicasWorkgroupsTwo-way exchange One-WayReplicaDisconnected ReplicasIdeal for outsourcing workXML-based transferTwo-way exchangeRead-Write AccessRead-Only AccessTuned for EditingTuned for ServicesCheck Out ReplicasAuthoritative ContentApproved ContentFile-based GDBInhouse or OutsourcedOne-time exchange 30. Multi-User ArcSDE PostGISFrancesc Puigvert 31. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 32. GIS Network ImpactWhat GIS Does ...- Graphic Data Representation (Maps)- Large Quantity of Data Analysis- Lots of Network TrafficDagwood Sandwich Network CommunicationsDistributed Clients Central Data Repository 33. Network Transport Time 34. Network Latency can make a difference Network latency is minimum communication packet travel time between client and server platformRule of thumb:GIS application with 20 layersmakes 200 round trips to theArcSDE Server. 35. Network Latency Example: 200 trips to server for single map display(i.e. 10 sequential round trips for each map layer 40 display layers)Local User Local Network (LAN)LatencyTransport TimeCPU Time0.001 sec(10 Mb / 10 Mbps)CPU Time200 tripsDBMS 0.66 sec 0.2 sec1.0 sec 0.05 secGIS User 2.00 sec per display, maximum 5.00 Mbps traffic (10 Mb/2.00 sec)Remote User500 miles (WAN) LatencyTransport TimeCPU Time 0.03 sec (10 Mb / 10 Mbps) DBMS CPU Time 0.66 sec200 trips0.05 sec 6.0 sec1.0 secGIS User7.80 sec per display, maximum 1.28 Mbps traffic (10 Mb/7.80 sec) (4 times slower than local environment)Latency reduces peak single user network utilization.Note: Message protocols (minimum chatter) perform best over high latency. 36. Network Traffic AdjustmentsOutput format adjustments 37. Network Traffic AdjustmentsData source adjustmentsSDE and File GDB about the same Shapefile traffic can be significant 38. Network Suitability Analysis1. Identify user workflowsIdentify average display traffic (Mbpd)Utilization100% 60%2. Identify user locations80%3. Compute workflow display traffic 60%Traffic = productivity (DPM) x Mbpd / 60 seconds40%4. Compute site traffic 20%Site Traffic = Sum (workflow traffic for that site)0% Traffic5. Identify Site Bandwidth6. Compute network utilizationUtilization = traffic / bandwidth 39. Network Suitability Analysis7. Calculate Workflow response times Response time Calculate network queue timesTransport time Queue time Calculate network transport times Network response time = transport + queue times + latency Calculate workflow display response times (Platform + Network response times) Validate user productivity Workflow Performance Summary1.6 Client(Adjust productivity as needed) 1.4Latency NWQ1.2 NetworkPerformance (sec)1.0WTSQ Response time Cycle time Computed Think time WTS0.8 WebQ Margin Minimum 0.6Webthink time MapQ0.4 Map0.2DBMSQ0.0DBMS8. Show Workflow Performance Summary 40. Application Types and Network LoadRich Client applications Heavy Load (10 Mb per display)RCA via Citrix(image) Medium (5 Mb)RCA via Citrix(Vector) Light (3 Mb)Web Apps(Dynamic) Medium (2 Mb)Web Apps(Cached) Medium (1 Mb)Services (REST) Medium (2 Mb)Services (SOAP) Medium (3 Mb)Mobile Apps Light (0.05 Mb) 41. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 42. ArcGIS System ------- ArcGIS Desktop -------ArcGISWebArcGISTerminalsArcInfo ArcEditorArcView--------- ArcGIS Engine ---------ExplorerBrowserMobile Terminal ServicesWeb Services ArcGIS Desktop ArcGIS Server Web GISArcGIS OnlineFilesGeodatabaseImageryMap Cache 43. Single-tier Platform ConfigurationStandard ConfigurationHigh-Availability Configuration Network Load Balancing GIS Web ServerGIS Web Server GIS Web Server WASWAS1 WAS2 SOM SOM1SOM1 Load BalancingSOM2SOC1SOC1SOC1 SOC2SOC1 SOC2SDE DCSDE DCSDE DC SDE DCSDE DC SDE DC DBMS ClientDBMS ClientDBMS ClientDBMS DBMS1DBMS2 DATADATA DATAWorkgroup Server with SQL ExpressEnterprise Server with SQL Express or other Supported DBMS Platforms 44. ArcGIS Server Image Extension. Single-tierTraditional ConfigurationHigh-Availability Configuration Single Server Multiple Servers Network Load Balancing AGS Image ServiceAGS Image ServiceAGS Image ServiceAGS SOMAGS SOM AGS SOMAGS SOC AGS SOC AGS SOCMosaic Data SetMosaic Data Set Mosaic Data SetImageryImagery Imagery AGS Image ExtensionAGS Image ExtensionAGS Image ExtensionData SourceData SourceData Source 45. Two-tier Platform ConfigurationStandard Configuration High-Availability ConfigurationGIS Web Server Network Load BalancingWASSOM1 GIS Web Server GIS Web ServerWAS1 SOM WAS2 SOC1SOC1 SOM1 Load BalancingSOM2 SDE DCSDE DCDBMS Client SOC1SOC2 SOC1 SOC2SDE DC SDE DCSDE DC SDE DC DBMS Client DBMS Client Cluster AddressDBMSDATADBMS DBMSGeodatabase ServerDATA Primary Data ServerFailover Data Server Common Storage Array Enterprise Server with Supported Database 46. Three-tier Platform ConfigurationsStandard Configuration High-Availability ConfigurationNetwork Load Balancing GIS Web Server GIS Web Server GIS Web ServerWAS1 WAS1 WAS2 SOM1SOM1SOM2SOM Load Balancing SOM Load BalancingSOC1SOC1SOC1SOC1SOC2SOC1 SOC2SOC1 SOC2SDE DC SDE DC SDE DC SDE DCSDE DCSDE DCSDE DC SDE DCSDE DCDBMS Client DBMS Client DBMS Client DBMS Client DBMS ClientDBMS ClientContainer Machine Container Machine Container Machine Container Machine Container MachineContainer MachineEnterprise Database Server DSEnterprise Database ServerDS 47. Votos y Cifras ExperienceFrancesc Puigvert 48. Votos y CifrasElections& data Web site -Elections Results -Elections historic results -Population Data (economic + demographic)Cloud AmazonServerEsri technology -ArcGIS Server workstation -JavaScript API -Tiled Maps 49. 1TV5 Newspapers 50. votos y cifras: Results331.065 Esri Espaa brand impacts -Direct presence in 18 regional newspapers website (Heraldo, Provincias, Verdad, Ideal,.) -More than 10.000 social networks impacts (Twitter, Facebook, eskup, Nolesvotes, -Daily record: 107.920 visits the 22-M.An average of 4 minutes remaining in the applicationDirect presence in the website of 4 national media (ElMundo, ABC, Publico y Telecinco)321.085 different visitors to our website from 29-04 to 23-05 51. Architecture DescriptionInstance m1.xlarge Extra Large InstanceJavaScript Web App 15 GB memory 8 EC2 Compute Units (4 virtual cores with 2 EC2 Compute Units each)Map Service 64-bit platformArcGIS Server + FGDB Tiled Map ServiceInternetAWS Esri InstanceBasic Unit 52. Elastic Load balancing Elastic Load balancing 12 4 2 53. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 54. User Expectations a closer look4.0Web IMS ArcIMS ADF ArcGIS Server ADFSS/SOC3.5REST ArcGIS Server REST MXDArcSDE MSD ArcGIS Server REST MSDDBMS3.0 Light complexity displayDisplay Performance (sec)2.5Medium complexity display2.0 Minimum user performance expectations.1.5 When is the software fast enough?1.00.50.0 IMS IMS IMS IMS ADF IMS ADF IMS ADF IMS ADF IMS ADF IMS ADF REST IMS ADF REST MSD IMS ADF REST MSD...2001 ...2002 ...2003 ...2004 ...2005 ...2006 ...2007 ...2008 ...2009 ...2010 ...2011 Calender Year 55. Map Display Complexity Only show relevant data - Start simple - Use field visibility Use scale dependencies - Appropriate data for given scale AGD10 wkstn MXD 100%Dyn 10x7 Feature - Same number of features at all scalesLocal FGDB Data Source Select the right point representationUse appropriate text and labeling - Use single layer simple or character markersUse annotation instead of labels - Use EMF instead of bitmaps Use indexed fieldsUse label and feature conflict weights - Use integer fields for symbol values sparinglyAvoid special effects (fill patterns, halos, - Avoid halos, complex shapes, maskingcallouts, backgrounds)Avoid very large text size (60+ pts) Select the right lines and polygonsAvoid Maplex for dynamic labeling (avoid - Use ESRI Optimized style overuse) - Avoid cartographic lines and polygon outlineThings to do to keep the map service time within performancebudgets 56. Classic dynamic mapping trade-offQuality vs. SpeedShaded reliefLow-resolution reliefTransparent layers Solid colorsMaplex labelingAnnotationExpensive functions Good performance 57. ESRI Optimized lines and polygons Outlines for all fills are simple lines instead ofcartographic lines Picture fills areEMF-based instead ofBMP-based ESRI Optimizedimproves drawingperformance by 50%+ ESRI Optimized improves performance 58. Use ArcGIS Optimize tool Analyze map directly from ArcMap (ArcGIS9.3.1+)- Analyze function included in Map ServicePublishing tools - Provides performance tuning recommendations- Preview allows for visual analysis of performanceand graphic quality - Provides optimized display rendering time 59. Display complexity (Mxdperfstat) Measuring MXD Desktop display rendering time (http://arcscripts.esri.com/details.asp?dbid=16931)Key performance metrics Display refresh times at multiple scalesLayer refresh times for each mapscalePerformance tuningrecommendations 60. Design PhasePerformance FactorsPerformance Test Cache vs. MSD vs. MXD2D Cache vs. Dynamic Data Response Time Comparison 6When possible, use 5Optimized Services for 4dynamic data.Single user Response Time (sec)response times 3are similar. 2If data is static, use 1 cache mapServices. 016 1116 21 26 31 36 41 4651User Count 2D Cache0.01 0.01 0.010.01 0.01 0.01 0.01 0.01 0.01 0.010.01 MSD 0.38 0.39 0.410.45 0.48 0.54 0.62 0.76 1.17 2.122.79 Dynamic 0.57 0.58 0.620.67 0.78 0.87 1.22 1.74 2.72 3.8 4.98Cache map services use the least of hardware resources.61 61. Web Mapping output image sizeSmaller mapstravel fasterPNG24 = 49 KBTraffic (56Kbps / 1.5Mbps)0.5 Mbpd (10 sec / 0.6 sec)PNG24 = 267 KBTraffic(56Kbps / 1.5Mbps) Based on REST MXD service 2.7 Mbpd (151 sec / 2.3 sec)- 600 x 400 resolution- 1280 x 1024 resolution (same display) Recommendation: Use reasonable output image sizeto support application while minimizing impact tonetwork 62. Web Mapping output image type Output Selection Response Image SizeTraffic56Kbps 1.5Mbps RASTERJPEG60 KB 0.6 Mbpd 13 sec 0.8 sec PNG24130 KB 1.3 Mbpd 36 sec 1.4 sec PDF180 KB 1.8 Mbpd 59 sec 1.9 sec Output Selection Response VECTOR ImageSize Traffic 56Kbps 1.5Mbps JPEG60 KB 0.6 Mbpd 13 sec 0.8 sec PNG24 50 KB 0.5 Mbpd 11 sec 0.7 sec PNG830 KB 0.3 Mbpd6 sec 0.5 sec PDF180 KB 1.8 Mbpd 59 sec 1.9 secHigh network trafficBased on REST MXD Servicereduces performance 600 x 400 resolution Recommendation: Use appropriate output type to support application while minimizing network traffic 63. Concurrent User Loads Service Instance Configuration (concurrent users)- Random arrival distribution reduces peak throughput- 3-5 instances per core provides optimum throughput- Display response time increases with max instance configuration Random arrival queuing delays Note: 4 core platform 16 (4x4) instances provide peak throughputWhat is optimum capacity setting? 64. Batch Process LoadsService Instance Configuration (batch processing) Batch process consumes a processor core N+1 Instances provide optimum throughput Batch run time increases with max instance configuration Workflow Performance Summary1.20DPM/TPM621 622 622622622 622 Client Latency 546 NWQNetwork1.00100% 100% 100% 100% 100% 100%Performance (sec) Tier 01Q Tier 01 88% Tier 02Q Tier 020.80 410 Tier 03Q Tier 030.60 66% Tier 04Q Tier 04 273 No random arrival queuing Tier05QTier050.40 Tier06QTier06 44% 137 Tier07QTier070.20 Tier08QTier08 22% Tier09QTier090.00 Tier10QTier101 234 5 67 8 9 10 1 2345 67 8 9 10 Batch ProcessesNote: 4 core platform 5 (4+1) instances provide peak throughput What is optimum capacity setting? 65. Memory recommendations Too many instances per server can exhaust memory- Increased paging when not enough memory- Slower processing due to shared compute resources- Maximum of 3-5 instances per core recommended Too few instances per server- Can limit utilization of hosthardware- Minimum of 3 instances percore recommended Provide sufficientmemory to supportoptimum performance- Minimum of 3 GB memoryper core recommended- More memory may berequired when using largefile data sources 66. Why should I care about map caches? Performance, performance, performance Scalability: Industry standard Cartographic quality ArcGIS Explorer Online 67. What should you cache? Base maps (always) Operational layers that satisfy one of the following: - High volumes of traffic - Dont change often - Cover small scales only 68. What about optimized map services? Optimized drawing format- Based on MSD file- Enhanced map drawing engine- Use to generated map tiles faster Does NOT replace cache map service- Requires dynamic rendering- Web services are optimized for cached tiles 69. Tile size Pixel dimensions of each image 256x256 is the web standard- 512 X 512 : legacy ArcGIS Online 256 Larger dimensions are faster tobuild, but tiles take longer todownload 256 70. Choosing an image format Image format effects - Tile storage space requirements - Web application performance (speed and supported browsers) - Tile image quality and transparency .JPG JPEG - Great compression for many colors but not transparency PNG - Best compression for less colors .PNG Mixed 71. Cached imagery workflow Prepare imageryPrepare - Build raster pyramids - Create mosaic dataset with overviews Author map documentAuthor - Add imagery to map - Save as MSD Publish as a map service Publish Create and manage the map cache - Configure cache definitionCreate - Generate cache tiles - Update cached tiles 72. Cache processing profile 500 total processing hoursSingle instance5 instances 10 instances (4 core server) (4 core server)(2 x 4 core servers)ArcSOC.exeArcSOC.exeArcSOC.exeArcSOC.exe ArcSOC.exe ArcSOC.exeArcSOC.exe Thread Thread Thread ThreadThreadThread Thread ThreadArcSOC.exe ArcSOC.exe ArcSOC.exeThread ThreadThread ArcSOC.exe ArcSOC.exe ArcSOC.exe ThreadThread ThreadArcSOC.exe ArcSOC.exe ArcSOC.exe500 hoursThread ThreadThread Thread Thread Thread125 hours 65 hoursTake full advantage of available hardware resourcesJ8338 73. Standard Performance Evaluation Corporation How do we measure relative performance?SPEC mission:To develop technically credible and objective benchmarks sothat both computer designers and purchasers can makedecisions on the basis of realistic workloadsESRI system design history19921996, SPEC92 benchmark results19962000, SPEC95 benchmark results20002006, SPEC2000 benchmark results2006+, SPEC2006 benchmark results SPEC benchmarks have served ESRI customers well 74. Geodatabase server 75. Two-Tier Configuration 76. Publishing services Francesc Puigvert 77. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 78. Desktop VirtualizationCustomer Experiencie and Motivations Simplified/Streamlined Administration Release control; Managing Upgrades WAN bandwidth and latency tolerance High availability for ArcGIS Desktop solutions Reduced client side requirements Specialized skill requirements for serveradministration and configurations to supportprinting, working with local data, etc. 79. Enhancing Desktopo Deployment - Infraestructure App/Session Virtualization+ High Availability+ Simplified Administration+ Network efficiency / WAN- 3D- System admin skill level~ User Experience 80. Server VirtualizationCustomer Experiencie and MotivationsIT StandardsAvailabilityDisaster RecoverySimplified/Streamlined AdministrationOther 81. Enhancing Server Deployment -- Infrastructure Hardware Virtualization+ High Availability+ Disaster Recovery+ Right sizing+ Staging environment- Performance risk 82. Example: Recommendations for VMWare Physical Machine:Physical Machine: 4 CPU/16GB RAM 4 CPU/16GB RAM VM: 1 CPU/4GB RAM VM: 1 CPU/4GB RAMVM: 4 CPU/16GB RAMSOM SOC WS SOCSOMSOCWSVM: 1 CPU/4GB RAM VM: 1 CPU/4GB RAM Physical Machine:SOCSOC 4 CPU/16GB RAM VM: 2 CPU/8GB RAMPhysical Machine: 4 CPU/16GB RAMSOMSOC WS VM: 1 CPU/2GB RAM VM: 1 CPU/2GB RAM VM: 2 CPU/8GB RAMSOM SOC WSSOC SOCVM: 1 CPU/2GB RAM VM: 1 CPU/2GB RAMOptimal Configuration SOC SOC4 VMs, 1 CPU/VM, 2GB RAM/VM 83. Recommendations for VMWarePenalty of virtualization (Physical vs. various VM configs)45000,00 32% Degradation11% Degradation40000,0035000,00 Throughput (Tr/Hr)30000,0025000,0020000,0015000,0010000,00 5000,000,00 1VM,4C,16R 2VM,2C,8R 4VM,1C,4R 4VM,1C,2R 1P,4C,16R Virtual Machine Configuration 84. Example: Virtual Server peaks of Works Web BrowserInternetIntranetSOM SOM SOC SOCSOC SOC SOC Direct Connects Direct ConnectsVirtual Server Physical Servers DBMS 85. Agenda: System Architecture Desing System Design Process GIS Technology Data Administration Network Communications Esri Architecture Performance- Software- Hardware Virtualization Example of CPT 86. Capacity Planning ToolFrancesc Puigvert 87. City of Portland - Solution ArchitectureCity Hall InternetT-115 Mbps1 Gbps LAN T-1 15 Mbps Sandy RiverMaintenance FacilityT-1 T-1 15 Mbps 15 Mbps 88. City of Mini-Portland - Solution ArchitectureCity Hall InternetT-1 15 Mbps1 Gbps LANT-1 15 MbpsMaintenance FacilityT-1 15 Mbps City of Minnie-Portland 89. User RequirementsArcGIS Desktop (Power, Editor, Viewer) Desktop (LAN), Citrix (remote sites)ArcGIS Server (Internal and Public web services) 90. User Workflow Requirements Suggested DESIGN procedure to build the city of Mini-Portland capacity planning model.- ArcGIS Desktop ArcInfo (AI) Power users - AGD10 wkstn MXD Med 100%Dyn 10x7 Feature - AGD10 WTS Citrix MXD Med 100%Dyn 10x7 V ICA- ArcGIS Desktop Editors - AGD10 wkstn MXD Lite100%Dyn 10x7 Feature - AGD10 WTS Citrix MXD Lite 100%Dyn 10x7 ICA- ArcGIS Desktop Viewer - AGD10 wkstn MXD Lite100%Dyn 10x7 Feature - AGD10 WTS Citrix MXD Lite 100%Dyn 10x7 R ICA- ArcGIS Server internal Web mapping application - AGS10 REST MXD Med 100%Dyn 10x7 R JPEG- ArcGIS Server REST MSD Public Web mapping application - AGS10 REST MSD Lite 100%Dyn 10x7 V PNG8 91. User Workflow Requirements- ArcGIS Desktop ArcInfo (AI) Powerusers - AGD10 wkstn MXD Med 100%Dyn 10x7 Feature - AGD10 WTS Citrix MXD Med 100%Dyn 10x7 V ICA- ArcGIS Desktop Editors - AGD10 wkstn MXD Lite100%Dyn 10x7 Feature - AGD10 WTS Citrix MXD Lite 100%Dyn 10x7 ICA- ArcGIS Desktop Viewer - AGD10 wkstn MXD Lite100%Dyn 10x7 Feature - AGD10 WTS Citrix MXD Lite 100%Dyn 10x7 R ICA ArcGIS Server internal and public Web mapping application 92. User Workflow RequirementsAGS10 REST MXD Med 100%Dyn 10x7 R JPEGand... Where is AGS10 REST MSD Lite 100%Dyn 10x7 V PNG8? 93. Favorites sheet 94. System Design 95. City of Mini-Portland - Solution ArchitectureCity Hall InternetT-1 15 Mbps1 Gbps LANT-1 15 MbpsMaintenance FacilityT-1 15 Mbps City of Minnie-Portland 96. Additional Resources System Design Process- http://wiki.gis.com/wiki/index.php/System_Design_Process Esri Press. Building a GIS- http://esripress.esri.com/display/index.cfm?fuseaction=display&websiteID=141 On-line resource center- http://esripress.esri.com/display/index.cfm?fuseaction=display&websiteID=141&moduleID=27 97. Additional Resources ESRI project methodology- www.esri.com/services/professional-services/methodology.html Business case resources- The Business Benefits of GIS: an ROI ApproachOutlines casestudies and general methodology for doing cost-benefitanalysis- Thinking About GISRoger Tomlinson- www.esri.com/getting_started/executives/success.html Project Management Body of Knowledge (PMBOK)- www.pmi.org 98. Thank You 99. Party 100. Thank You