<div dir="ltr"><div>Hi all.</div>
<div> </div>
<div>I am having issues with MapGuide 2.0 versus the 1.2 release with regards to WMS performance.</div>
<div> </div>
<div>
<div>I am making 28 asynchronous WMS requests to the MapGuide server in order to retrieve tiles.</div>
<div>This is on IIS configuration. Same data set.</div>
<div> </div>
<div> </div></div>
<div>With MapGuide 2.0:</div>
<div> </div>
<div>Dual Core test box: each tile can take 3 - 15 seconds to retrieve depending on request order with an average of 10 seconds.</div>
<div>4 Dual Core Processor server (8 Cores): each tile can take 3 - 15 seconds to retrieve depending on request order with an vaerage of 10 seconds.</div>
<div> </div>
<div>There is no indication that the isapi dll is taking advantage of the extra cores.</div>
<div> </div>
<div>When viewing the map in ajax or fusion the map is drawn in 3 seconds or so.</div>
<div> </div>
<div>The option to tune the FastCGI is not present in the Registry</div>
<div> </div>
<div> </div>
<div>With MapGuide 1.2:</div>
<div> </div>
<div>
<div>Dual Core test box: each tile can take 2 - 5 seconds to retrieve depending on request order with an average of 3 seconds.</div>
<div>4 Dual Core Processor server (8 Cores): each tile can take 0.5 - 3 seconds to retrieve depending on request order with an vaerage of 1 second.</div>
<div> </div>
<div>The FastCGI has been configured to take advantage of the extra cores.</div></div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div>So the 1.2 release is 100% faster with regards to WMS requests on a properly configured server.</div>
<div> </div>
<div>Has anyone experienced the same or similar issue? </div>
<div>Is there a way to tune the 2.0 release ISAPI filter?</div>
<div> </div>
<div> </div>
<div> </div>
<div> </div>
<div>Cheers,</div>
<div> </div>
<div> </div>
<div>Kori Maleski</div></div>