Menu

Improving performance

Developers
2005-10-28
2013-04-17
  • John Pulles

    John Pulles - 2005-10-28

    The performance of mappingwidgets is (partly) determined by the amount of html/javascript code that is transferred from server to client. At present only serverside caching is done by smarty.

    An improvement seems to be possible in 2 parts:
    1) introduce client side caching by putting the javascript code in separated files (per language!) and using <script src=file.js>.
    2) compress the javascript code

     
    • John Pulles

      John Pulles - 2005-10-28

      A first implementation doesn't yet take language codes in the javascript files in account.

      The difference of the generated page (one with most buttons, a simplemap, a simplelegend and an overview) is large: with code included the size of the page is 73.4 kB, with the javascript as src files it is only 10.8 kB.

      Note that client caching also requests less capacity from the server.

       
    • John Pulles

      John Pulles - 2005-10-28

      A suitable compression has not been found yet, but an approximation is that e.g. SimpleMap.js can be compressed from 45 kB to about 24 kB.

       
      • John Pulles

        John Pulles - 2005-10-28

        A working compressor is found at http://dojotoolkit.org/docs/compressor_system.html
        It compresses SimpleMap.js from 45.2 kB to 23.5 kB (a 48% reduction).

         

Log in to post a comment.

MongoDB Logo MongoDB