1. tiling once done should be a use benefit once tiled 2. the javascript compression will only aid initial page load times
what's your data like? if it's too detailed, that will slow down your server ie if you have 5mm resolution data being rendered at 1:100k, that's a lot of overhead z On Fri, Sep 24, 2010 at 5:29 PM, findjai <[email protected]> wrote: > > Hi All, > I am a user of Mapguide 2.0 version... In general i have found it is > slower on clients browser. I wish if you all can help me in order quicken > mapguide. > I have tried a few suggestion i found on the internet. > 1) Tiling - It does not increase the speed rather it slows down the process > :( . Does it also depend on tile size? if yes, what can be optimum size. > 2) One of the patches provided by Zac to compress javascript ... i tried but > could not see any visible difference :( > Thanks all, > Jai > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/Regarding-Tips-to-speed-up-mapguide-tp5565830p5565830.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users > -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia http://www.ennoble.com.au http://zacster.blogspot.com +61 405 847 168 _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
