-
-
Notifications
You must be signed in to change notification settings - Fork 385
What is the maximum WCS export size #4421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Same problem here, but with regular WMS request. MapServer: Debian GNU/Linux 6.0.7 (squeeze)
|
@7o9 what's the request URL ? |
Works fine up about 23000 by 23000 pixels but we need up to ~70000 by 100000. Processing times is exceptionally fast, needs about 10 seconds for a map that needs 20 minutes rendering using ArcSomething... It is used for high resolution printing. |
Is there anything else running on the server? i.e. do you have the 3.5 Gbytes of ram available for that allocation ? |
also note that your 70000*100000 requests are each going to require 28Gb of memory, which is clearly going to fail on a 16Gb server |
@7o9 maybe check your ulimits ? |
What is the formula for calculating the required RAM? |
width_height_4 , result in bytes |
Thanks. We can adjust resolution to fit the server / stock up on RAM. But this does not solve the original problem. The request only requires 3.6 GB as per your formula and there are definitely ~15GB available?! |
After some playing around I think we have a hard limit of 2GB somewhere in MapServer. I can request up to 23k square images, anything more will break things. Makes sense? |
yes, makes sense... that's what my "check your ulimits" idea was for |
Ah, I misunderstood you then. I thought you suggested limits of image size... What is "ulimits" & where can I check / set them (outing myself as a noob). |
I've never tinkered with them personally. check out https://wiki.debian.org/Limits , and more precisely |
...later, rechecked all: MapServer is 64bit binary running on a 64 bit system with sufficient RAM. The Apache processes are running as user www-data and: But we do get a segmentation fault: So I still suspect that it is some hard-coded limit in MapServer or one of its libraries. |
This issue is very easy to reproduce, simply call a WMS request with a width and height exceeding 25000 pixel. Always works, like in: always breaks. |
Questions belong IMHO better to mapserver-users mailing list. Three years later I asked the same question because I do not follow Github issues so closely. I suppose that this ticket does not deal with any exact bug so I am closing it. |
for a 64 bit instance
I'm getting messages like
when making large (5 sq mile) wcs requests (1.0.0) against a tile index with resolution of (0.1 m).
The text was updated successfully, but these errors were encountered: