Depending on what you're doing, any bulk requests should be to a
pre-seeded MapCache and not the WMS server per se. In a production
environment a modestly detailed raster, it's easy to kill a WMS server
of any size.
You're going to have to test a range of requests to get a usable setup.
You may even consider limiting the size of bounding box requests.
On 4/20/23 06:59, Oskar Ravhed wrote:
It is impossible to answer on without knowing what kind of for
wms/wcs/wfs you are serving with mapserver
For example a simple raster wms will be able to do many request per second.
On the other side serve out osm from a postgis database will in some
heavy scale not do more then 1 tile every 5 second
I would determ it based on cpu/disk usage instead of request per second
On 20/04/2023 15:48, Marcin Niemyjski via MapServer-users wrote:
Hello
I'm looking for a benchmark advice.
If I have a machine running on 6 CPUs and 25gb RAM what would be the
value of the number of requests per second from which I should start
scaling my VMs with Mapserver?
Is there any way of testing or investingating? I'm using Locust and
JMeter but it's really hard to get a logical answer for this question.
Best,
Marcin
<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae9486487...@cloudferro.com?anonymous&ep=signature>
Book time to meet with me
<https://outlook.office.com/bookwithme/user/6347c7def05a478ba013ae9486487...@cloudferro.com?anonymous&ep=signature>
_______________________________________________
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________
MapServer-users mailing list
MapServer-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users
