Map browsing is one of the most frequently used operations of GIS. The drawing performance quality directly affects the user experience. But how to test the drawing performance in a fast way? Let’s recommend an efficient tool, that is LoadRunner. It can confirm and search problems through the way of simulating the concurrent loading and real time performance monitoring. Besides, LoadRunner can test the entire enterprise architecture. The following parts will show the whole process that LoadRunner tests the drawing performance of GIS server based on SuperMap iServer 9D.
1. Record the scripts
Before performance testing, you need to prepare the test scripts first. Open the LoadRunner and choose Create/Edit Scripts, then launch VuGen to record the scripts.
2. Modify the scripts
a. Increase the number of drawing pictures.
While recording the scripts, we only draw one picture. But what the users browse are the full screen pictures. Therefore, the scripts need to be modified. Copy the script bellow and modify the index value of x and y of the tile. Then increase or decrease the value of x and y in turn to get the other tiles around. (Please make sure that the index value of both x and y does not exceed the map range.)
b. Insert the web_concurrent function.
Usually, when there are multiple requests in the scripts, the LoadRunner will process them one by one. This is conflicted with the parallel requests of the browser. We can insert web_concurrent_start function before drawing and insert web_concurrent_end function after drawing. Then the requests can be sent in parallel between these two functions.
c. Insert the transactions.
As the transactions are the only method for the LoadRunner to measure the performance index, we need to insert the transactions to calculate the response time of the system.
3. Layout design and operation.
Save the scripts after modifying. Then go to controller components to process the layout design and operation through the path of Tools - Create Controller Scenario - OK.
a. Add load generator
b. Design and operate layout
4. Results analysis
Go to analysis components from controller components (tool--analysis) to analyze the results.
a. According to the results of the throughput rate, we can check if the network bandwidth reaches the maximum value in the case of high concurrency. If it’s true, we need to upgrade the network bandwidth.
b. From the user map, server CPU and the real time consumption of memory, we can confirm whether there is memory leak of GIS server or over high occupancy of CPU.
c. Through real time monitoring of the consumption of transactions CPU, memory and network bandwidth, we can ensure that the performance of the test will not be reduced due to insufficient load CPU, memory or network bandwidth. The user data graph can be superimposed with other data graphs to check the performance data.
Thus, the whole performance test process has been finished. With the four steps above, you can deploy your own GIS test tasks. Isn’t it simple? Let's try it!
Satellite Tracking + Big Data GIS Application in Real-time Ship-controlling>
Big Data - Signaling Data Makes Cities Smarter>
