[mapguide-trac] #175: Unmanaged SHP File Locations Performance Issues as More Files get Added

[MapGuide Open Source]

#175: Unmanaged SHP File Locations Performance Issues as More Files get Added
-----------------------------------------------+----------------------------
 Reporter:  cgountanis                         |         Owner:       
     Type:  defect                             |        Status:  new  
 Priority:  high                               |     Milestone:  1.2  
Component:  Server                             |       Version:  1.2.0
 Severity:  major                              |    Resolution:       
 Keywords:  fdo,mapguide 1.2 beta 2, shp, dbf  |   External_id:       
-----------------------------------------------+----------------------------
Comment (by amorsell at spatialgis.com):

 Along those same lines, I have discovered that displaying tooltips from
 unmanaged shape files causes a much more significant performance hit and
 delay.  In my case, I have a 150 MB parcel polygon shape file for a
 county.  In the unmanaged case, each tooltip AJAX fetch spikes the CPU
 with mgserver.exe at 100% for a couple of seconds.  Doing the same with
 the exact same shape file in a managed state (not converted to SDF at load
 time), the CPU will only hit 25% or less and responds much more quickly.

 Further, I discovered that the more unmanaged data in a map, the slower
 the tooltip response is for all layers.  For instance, if I add another 7
 or so layers (like streets, water bodies, etc) to the map, when I float
 over a parcel polygon it can take up to 10 seconds for a tooltip response
 during which time mgserver is cranking away.  So, I'm not sure what it's
 doing at that point.  All of these additional layers are all in the same
 unmanaged data source folder.

 I went ahead and loaded all of the shape files into the repository and
 created a duplicate map pointing to the new managed feature sources.  This
 map behaves fine with tooltip fetches consuming 25% of a single CPU and
 very quick response time.  So, this seems to confirm that the more
 unmanaged feature sources in a map (at least from the same directory), the
 larger the performance hit and the slower the map responds to requests.

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/175#comment:2>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals