Understanding the Performance Report of AIMS2013

By Daniel Du

In AIMS 2013, a new performance report tool is introduced in Map Administrator(http://<machinename/mapserver2013/mapadmin/login.php). This tool can be used to analyze the performance of your map server to find out the performance bottle neck. BTW, if your performance report does not work for you, this post may be helpful for you.

Before we start, here is some background knowledge, every time we view a map in AIMS, actually we see a part of the map, it is a image which size is a little bigger than your visible area in the browser. Different part of the map and different zoom level of the map will cost different time to render it. That ‘s why we need to specify an area and also the zoom level to get the performance report when running this tool.

This is a performance report of my test data:

The tag “Layers” means the time spent on layer rendering, including FDO connection, feature query and layer stylization;

Tag “Images” means the time spent on image creation, in other words, compress imagebuffer to a bytesstream in given format (PNG, JPG);

Tag “Other” includes other time spent on map rendering except layers rendering, selection rendering, watermarks rendering, label rendering and image creation. For example, create a Renderer in memory, create the map’s coordinate system, etc..

For my performance report, it seems that my rendering performance is pretty good, the “Layers” tag is only a small percentage, because I have only 4 layers to render. Detailed rendering time cost for each layer is listed below:

If you have many layers to rendering, you probably want to find which ones are the bottle neck, then try to tune them up accordingly.

Do you think this tool useful? In next post, I will introduce how to use profiling API, which makes it possible to create your own performance report tool. Stay tuned!