Hi all. I am having issues with MapGuide 2.0 versus the 1.2 release with regards to WMS performance.
I am making 28 asynchronous WMS requests to the MapGuide server in order to retrieve tiles. This is on IIS configuration. Same data set. With MapGuide 2.0: Dual Core test box: each tile can take 3 - 15 seconds to retrieve depending on request order with an average of 10 seconds. 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. There is no indication that the isapi dll is taking advantage of the extra cores. When viewing the map in ajax or fusion the map is drawn in 3 seconds or so. The option to tune the FastCGI is not present in the Registry With MapGuide 1.2: Dual Core test box: each tile can take 2 - 5 seconds to retrieve depending on request order with an average of 3 seconds. 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. The FastCGI has been configured to take advantage of the extra cores. So the 1.2 release is 100% faster with regards to WMS requests on a properly configured server. Has anyone experienced the same or similar issue? Is there a way to tune the 2.0 release ISAPI filter? Cheers, Kori Maleski
_______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users