Also combining all javascripts into one file helps. Using separate files is useful for debugging your application, but for performance you want to combine all files into one single 'compressed' file:
http://www.communitymapbuilder.org/display/MAP/Compressing+Mapbuilder regards, Steven Cameron Shorter wrote: > Check what "plain old layers" you are using. > What version of Mapbuilder are you using? > I think the default WMS layer in version 1.5 are tiled. > > Have a look at the mapbuilder debugging page for ideas. In particular, > use firebug to view the images loaded into your page (to see if they are > tiled). > > Another thought. > Browsers often only download 2 images at a time from each domain name. > So image 3, 4 won't start downloading till 1, 2 have finished. > > You can get around this by providing multiple domains for your WMS. > http://wms1.wms.org http://wms2.wms.org > > > Marcos Sánchez Provencio wrote: > >> El mar, 17-07-2007 a las 22:16 +1000, Cameron Shorter escribió: >> >> >>> A few questions which could make a difference: >>> What layer types are you using? >>> * If you have a tiled layer, you probably have 12 or so images per >>> layer. This can be reduced by reducing the buffer size, or even better, >>> switch to WMS images. >>> >>> >> I am using plain old layers. The images themselves are quite fast once >> the page is loaded. >> >> >> >>> * If you are using vector data, how big are your vector files? You might >>> do better to render on the server as WMS. Which version of Mapbuilder >>> are you using. 1.0 uses slow WalterZorn vector rendering. 1.5 uses >>> SVG/VML. SVG on Firefox is faster than VML on IE. >>> >>> >> I am serving bitmaps already. >> >> >> >>> -- >>> >>> Have you tested to see where the bottleneck is? Is it on the server or >>> client, or in transporting large files from server to client? >>> >>> >> The bottleneck seems to be in executing javascript code in the client. >> This is compatible with the fact that performance is so different >> between FF and IE. Curiously, FF sets CPU at 100% in the client while >> seemingly waiting for responses, but IE does not. >> >> >> Thank you very much. >> >> >>> Marcos Sánchez Provencio wrote: >>> >>> >>>> Hello everybody. >>>> >>>> I am building a meteorological application. I need to show 20 or 30 maps >>>> (5 signals, every hour, for 5-6 hours). I also want to show some fixed >>>> information (boundaries, rivers...). This is extremely slow in IE and >>>> slow on FF. I have tried to profile this problem but have no results >>>> whatsoever (except for the scalebar to be especially slow). >>>> >>>> Is there some way to accelerate the creation of controls, for example, >>>> by bypassing the xsl transformations and instanciating DOM objects in >>>> some way? >>>> >>>> Why is it so extremely slow in IE? Has anyone used mapbuilder to show >>>> many maps? >>>> >>>> Just in case it help, this is what the result screen looks like: >>>> http://burke.ath.cx/~marcos/f/Pantallazo.png >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by DB2 Express >>>> Download DB2 Express C - the FREE version of DB2 express and take >>>> control of your XML. No limits. Just data. Click to get it now. >>>> http://sourceforge.net/powerbar/db2/ >>>> _______________________________________________ >>>> Mapbuilder-users mailing list >>>> [email protected] >>>> https://lists.sourceforge.net/lists/listinfo/mapbuilder-users >>>> >>>> >>>> >>>> >>> >>> >> >> > > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Mapbuilder-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-users
