<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Jeff<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks for the tip and code snippet! Could you add a wiki entry with this tip? That will make it more accessible for people to find and make it easier to
add to the GeoMOOSE trunk. The wiki is at: <a href="http://www.geomoose.org/wiki/index.php/User_Tips/Code_Snippets">
http://www.geomoose.org/wiki/index.php/User_Tips/Code_Snippets</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">There is a link in the upper right-hand corner to create a logon.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Len<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Jeffrey Schmitz [mailto:jeffreykschmitz@gmail.com]
<br>
<b>Sent:</b> Thursday, January 13, 2011 2:08 PM<br>
<b>To:</b> geomoose-users@lists.sourceforge.net<br>
<b>Subject:</b> [Geomoose-users] How we cut our load time in half<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hey Everyone,<br>
<br>
I'm not sure if this is the best place to post this, so please let me know if there is a better place to send it. Anyways, we were able to cut our page load time in half for our geomoose instance, and I thought I'd post it on the mailing list in case it might
help someone else out. Using firebug, we were able to determine that Geomoose's itereateThroughLayers function was taking a significant amount of time, so we looked for a way to improve it. We ended up coming up with a solution that is slightly more memory
intensive, but cut the time spent on the function in half. To implement the change, just replace the old iterateThroughLayers function with the following code (in compiled.js):<br>
<br>
var theLayer = new Array();<br>
var pathsP = new Array();<br>
function iterateThroughLayers(pathString, fn) {<br>
if(pathsP[pathString] == null){<br>
var services = MyCatalog.getElementsByTagName('map-source');<br>
var paths = new String(pathString).split(':');<br>
for(var i = 0; i < services.length; i++) {<br>
var root = services[i].getAttribute('name');<br>
var layers = services[i].getElementsByTagName('layer');<br>
for(var l = 0; l < layers.length; l++) {<br>
var layerName = layers[l].getAttribute('name')<br>
for(var p = 0; p < paths.length; p++) {<br>
if(root+'/'+layerName == paths[p]) {<br>
var mapLayer = Map.getLayersByName(root)[0];<br>
theLayer[pathString] = mapLayer;<br>
pathsP[pathString] = paths[p];<br>
if(mapLayer) {<br>
fn(mapLayer, paths[p]);<br>
}<br>
}<br>
}<br>
<br>
}<br>
}<br>
}<br>
else{<br>
if(theLayer[pathString]){<br>
fn(theLayer[pathString], pathsP[pathString]);<br>
}<br>
}<br>
<br>
}<br>
<br>
This works because the function is hit twice with the same pathString (just a different function), and unnecessarily has to run through the same series of identical loops twice. Instead, the information genorated from the first run through is stored in the
two arrays theLayer and pathsP and recalled. <br>
<br>
This may not significantly improve speeds if you are not using many layers, but if you are, you should see some gains. I hope this helps some people out!<br>
<br>
-Jeff<o:p></o:p></p>
</div>
</body>
</html>