09-25-2017 02:36 AM
What should be the criteria for setting up number of map servers for GeoMedia WebMap. What should be the thumb rule for better performance with 100 concurrent users?
Though performance will depend on various factors like number of layers, type of database etc. But is there any document available to estimate the server sizing?
09-25-2017 02:42 AM
regarding the number of MapServers, I think it is meaningless to set it to anything bigger than the number of physical cores/processors of your server.
09-25-2017 03:19 AM
Yes, but I saw that by default, when we install WebMap, it takes number of map server = number of physical cores / 2.
So is there any rule or documentation to decide on how to define the number of map server?
09-25-2017 06:01 AM - edited 09-25-2017 06:09 AM
But I think this document has considered WMS. How about the editing users who are using WFS-T or WFS and also for WMPS. Since the average processing time for each Map request can be more so how much time should be considered for these services?
09-25-2017 07:28 AM
It is very difficult to provide that level of guidance for each customer as every GeoMedia WebMap implementation is unique in terms of usage and configuration.
From my own experience the best advice I can offer you is to performance test your infrastructure to identify the bottle necks in your architecture and optimise as necessary to meet expected/required performance levels.
Also consider (if you can) seperating out your web services across web server pools to improve through-put and availability. This should also allow you to run infrequest but long running web service requests (such as WFS and WMPS) seperately from frequent web service requests (WMS and WMTS) so the profile usage of the GeoMedia WebMap Map Servers is suited to to the requests received by the server pool.