GDB Performance Concerns

Discussion created by merlich on Aug 17, 2011
Latest reply on Aug 24, 2011 by MBranscomb-esristaff
We converted some shape files that cover 3 states in the U.S. from TeleAtlas data consisting of 11 layers (highway exits, institutions, landmarks, highways, railroad, streams, streets, parks, water, counties, and cities).  The zoom level of when to show each of the layers was optimized to where ArcMap could perform well (set to a lower minimum than we would probably use in production).  The shape files were converted to the geodatabase format (using feature class to geodatabase conversion tool).  After the mpk was created, it took 55 seconds to load the map from the time the application loaded to the time the maps were actually displayed.  To do a query using the QueryTask by searching for a city name in the streets layer, it took 40 seconds.

Are there other formats the data can be converted to for better performance, or does the control not handle large data-sets?

These tests were performed on a dual quad-core (2GHZ each) with 8GB RAM on an x64 machine.  Our typical use case is for this to run on client machines with the data locally with a single processor (1.2GHZ) with 1GB RAM.