[mapserver-users] Controling the amount of concurrent GetMap requests

Mark Korver mwkorver at gmail.com
Thu May 26 17:01:10 EDT 2011


I would think that the thinking here is that a server only scales well
to some number of concurrent requests.  That beyond that number, all
requests suffer.  In this case it's better to queue the requests
rather than try to process them, meaning queuing improves performance
overall.

On Thu, May 26, 2011 at 1:57 PM, Stephen Woodbridge
<woodbri at swoodbridge.com> wrote:
> On 5/26/2011 12:52 PM, Asad Ullah wrote:
>>
>> List,
>>
>> Does anybody know how to control number of concurrent GetMap requests in
>> MapServer?
>
> You can't do this within mapserver because each instance of mapserver is not
> aware that there are any other instances running. Presumably, you would have
> to look at Apache or IIS and see what controls there are to limit concurrent
> requests to a URL or something like that.
>
> I more basic question in my mind is what do you want to happen if this limit
> is exceeded. What would you expect the user experience would be if you were
> to make a limit+1 request? would it get rejected, queued up until another
> request finished?
>
> Anyway probably not a mapserver question other than to say mapserver does
> not do this.
>
> -Steve W
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>


More information about the mapserver-users mailing list