Hi ThinkGeo,
What is the recommended configuration to deploy web and WMS from performance view point?
1) Should they be on the same server or different machine?
2) Nowdays machines have multi-core processors...does WMS and Web component take advantage of multi-processors?
Regards,
Anil
Hi, Anil
There is no need to deploy the web app and the WMS Server on the same machine. If you do it in this way, I guess it will increase the load on the server and reduce the response time for the tile images.
A WMS server solution allows you to separate the map generation away from the main set of web servers. This may be important if you can handle the normal web load on one server but adding mapping seems to bog it down. This becomes a problem because web request such as generating a report or saving a record to SQL has to compete with generating lots of maps. Map generation is very time and resource intensive so if you can isolate it you are better off. This allows your web traffic to other parts of the website to not have to compete with map traffic.
The technology in the WMS server allows you to server maps faster than in the web edition. In the WMS server we have a concept of a map configuration that you setup for a certain set of maps. The WMS Server will create as many of these as it needs to handle the number of requests in relationship to how many cores the machine has. In this way we can be very aggressive with utilizing all the resources of the machine because we assume it is for the single purpose of generating maps and serving them. In the Web Edition we have to live in the rest of the ecosystem and be more conservative. In addition we have special logic for static maps that allows us to generate them more efficiently.
Thanks,
Khalil