[mapguide-users] Re: fusion viewer performance vs basic viewer

[Jackie Ng]

Fusion is really heavy with javascript and demands a modern browser for
optimal performance. IE7 does not classify as a modern browser.

>From our experience, the primary bottleneck is the legend widget and its
woefully inefficient method of retrieving legend icons, which is magnified
with the number of layers you have. You do not see the issue in the AJAX
viewer because 

My github fork (https://github.com/jumpinjackie/fusion-multimap) has
addressed the map loading and legend performance issues, but sadly this
solution uses techniques that are only supported by a modern browser. I have
yet to port these changes back to the official fusion repo due to other
changes to support multiple maps being broken in fusion trunk. The two
features are somewhat intertwined, making it somewhat hard to cleanly port
over, especially when one part is absolutely broken.

If you *really* have to use IE, make it at least IE8, but if you can you
should really go for IE9. It is actually a half-serious attempt at a modern
web browser from Microsoft. In actual fact, IE9 actually performs better
than Firefox/Chrome from my tests with both Fusion and AJAX viewers. I was
actaully blown away when I saw the AJAX viewer load in a blink in IE9, where
it took several seconds on Firefox and Chrome.

So I would only go with Fusion if you can standardize on IE9/Firefox/Chrome.
These are the browsers with enough grunt to handle the javascript. If this
is not possible, then you probably have no choice but to stay with the AJAX
viewer. Not that it's a bad thing, the AJAX viewer is tried and tested.

- Jackie

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/fusion-viewer-performance-vs-basic-viewer-tp6824506p6824779.html
Sent from the MapGuide Users mailing list archive at Nabble.com.