I don't think it's possible to have some generic figures. It depends on data and data organization, scale dependency, number of layers to process for 1 map request, processing power of the server and number of CPU cores, connection bandwidth, etc.
Also what is the definition of "concurrent users"? The main issue is how many map images can be requested contemporaneously and still produced by the server in acceptable time (but what is "acceptable" ...?). Since a user requests a new map maybe just every 5 or 8 seconds... There are some figures from Foss4G conferences how many requests Mapserver can serve via WMS and CGI. Some tests I made some time ago showed that PHP/Mapscriipt requests using Apache module for PHP are lying between CGI and fast-CGI, and the main factor of response times in p.mapper is the pure map creation (95 % or more...) armin On 28/11/2011 02:16, salo wrote: > > Hello, > > Can anyone tell me, which is the recommended number of concurrent users to > pmapper? > > Thanks! ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
