As an Administrator of a GeoMedia WebMap implementation I need a scalable solution for handling map requests for large datasets and the ability to run multiple web services from a single server.
As the core underlying GeoMedia API will remain on a 32-bit architecture as confirmed here the Map Request process operated by the Map Server Manager and Map Server processes should be optimised to work more efficiently within the memory limit of a 32-bit process. Customer expectations are that Hexagon software should be able to utilise the modern architecture they have available to them such as multi-core servers with large amounts of memory i.e. do more with less.
When running multiple web services (15 or more) from a single server the memory usage on a MapSvr.exe can be large once all Service Sources are initalised leaving limited available memory to handle map requests sent to the web services. The only way to implement a large web service implementation is to spread web services across multiple servers. This is deemed costly by customers due to the costs associated with licensing Hexagon and third-party software on additional servers.
One possible method to optimise memory usage with MapSvr.exe processes would be define pools of Map Server processes. The Map Server Manager would then pass requests from certain web services to a particular pool of Map Server processes to handle.
As an Administrator I would benefit by being able to utlise the server architecture more efficiently with a single WebMap implementation ensuring the most used web services have a dedicated pool of Map Server processes.
This architecture is similar to how the Hexagon NetWorks product Map Server processes operate.