<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16441" name=GENERATOR>
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2>First, I love the unmanaged resource concept and will most
likely deploy most future MGOS applications this way.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2>But, similar to Chris' problems, 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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2>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. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007><FONT face=Arial
color=#0000ff size=2>I have appended this information to the TRAC ticket that
Chris started earlier today.</FONT></SPAN><SPAN
class=109573419-25052007></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=109573419-25052007></SPAN><SPAN
lang=en-us><FONT face=Tahoma size=1>Andy Morsell, P.E.</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Tahoma size=1>Spatial Integrators, Inc.</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Tahoma size=1><A
href="http://www.SpatialGIS.com">http://www.SpatialGIS.com</A></FONT></SPAN>
</DIV>
<DIV>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mapguide-users-bounces@lists.osgeo.org
[mailto:mapguide-users-bounces@lists.osgeo.org] <B>On Behalf Of </B>Chris
Gountanis<BR><B>Sent:</B> Friday, May 25, 2007 7:52 AM<BR><B>To:</B> 'MapGuide
Users Mail List'<BR><B>Subject:</B> [mapguide-users] Unmanaged SHP File
Locations<BR><B>Importance:</B> High<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Why do unmanaged FeatureSources
respond slower as more files get added to the directory location? We have a
FeatureSource called SHPDefualt for example. The zooms take longer as well as
other functions. It seems when you query a Feature Source is does not hit the
DBF you want directly it seems to fiddle with everything in the unmanaged
directory. We love the concept of a folder that contains all SHP files. One
location is great for batch processes and great for editing new layers. It is
just simple for customers to understand. For sure easier to back up and
recreate. Will this always be a performance killer?<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is this a bug? Will this be fixed
soon?<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">This really takes the complication
out of knowing what the heck is going on in the repository. Here is XML
Example:<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><?xml version="1.0"
encoding="utf-8" ?> <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><FeatureSource
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><Provider>OSGeo.SHP</Provider>
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><Parameter><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><Name>DefaultFileLocation</Name>
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><Value>C:\SHPFILES</Value>
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></Parameter><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></FeatureSource><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><B><FONT face=Tahoma color=darkblue size=3><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 12pt; COLOR: darkblue; FONT-FAMILY: Tahoma">Chris</SPAN></FONT></B><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P></DIV></BODY></HTML>