Rendering performance of SVG Map
This page is English Version of the Japanese article of this blog.
We achieved the rendering performance comparison of the mapping platform following the article on the storage efficiency. The data used for it are as follows.
- The coastlines in Japan which makes the GLOBAL MAP an origin
SVG:0.9MB, GeoJSON: 1.6MB, KML: 2.3MB - The roads in Japan which makes the GLOBAL MAP an origin
SVG: 10MB, KML: 29MB - The river lines in Australia which makes the GLOBAL MAP an origin
SVG: 54MB
Among these, the data of 1 and 2 is the one having used it in the article before.
The environments used are as follows.
| SMT | SVG Map Toolkit 0.6 |
| FFX | FireFox3.0.1 |
| OPR | Opera9.5 |
| ASV | Adobe SVG Viewer 3.0 |
| REN | Renesis Player 1.0 |
| OLI | OpenLayers 2.6 / Internet Explorer6 |
| OLO | OpenLayers 2.6 / Opera9.5 |
| OLF | OpenLayers 2.6 / FireFox3.0.1 |
| GMI | Google Maps / Internet Explorer6 |
| GEO | Google Earth 4.3 |
Performance measurement results concerning data "1" (unt:[seconds])
| SVG | GeoJSON | KML | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| SMT | FFX | OPR | ASV | REN | OLI | OLO | OLF | OLI | GMI | GEO |
| 0.6 | 1.5 | 1.2 | 1.7 | 0.7 | Hang up | 9 | 11 | Hang up | Stall | 2.5 |
Performance measurement results concerning data "2"
(OpenLayers and GoogleMaps dropped out. )
| SVG | KML | ||||
|---|---|---|---|---|---|
| SMT | FFX | OPR | ASV | REN | GEO |
| 2 | 19 | 11 | 17 | 6 | 43 |
Performance measurement results concerning data "3"
(KML dropped out. )
| SVG | ||||
|---|---|---|---|---|
| SMT | FFX | OPR | ASV | REN |
| 11 | 51 | 34 | 48 | 17 |
Processing speed of SVG Map Toolkit was the highest among these. It is because it is tuned by paying attention to the rendering performance of map data.
On the other hand, though this was expected, viewers coded with javascript (OpenLayers and Google Maps) seems to be far behind native code viewers, in the point of the performance. It seems that a lot of various resources were consumed, and operation was also unstable.
The display of the vector data may be very important for the map services. And, we are considering that drawing of the vector data at "1" level should be able to be executed easily. (If it is a compressed format (.svgz), such data is a suitable size for today's WWW.) However, it might be considerably difficult for today's ordinary PC as long as it depends on javascript viewers.
