On vendredi 2 juin 2017 05:57:25 CEST Schepers, Benjamin wrote: > Hi Daniel, > > thanks for your advice - I've done exactly the same way you as you described > it for some years now (doing the painful "average"-resampling due to > preprocessing the overviews with GDAL and nesrest in WMS-postprocessing). > The servers and services are "highly optimized" and generally fast - thanks > to GDAL's and mapserver's functionality and performance and community > hints. But I wasn't really satisfied with final image-quality, because of > the trade-of between performance and image-quality on WMS-postprocessing - > I decided for performance. > From my point of view it still makes a difference in image quality, whether > I use nearest or average on WMS-postprocessing, especially the > aliasing-effects on edges of buildings, bridges, etc. would be nearly > totally eliminated with "average"postprocessing , I did some tests! > My guess was, that resampling could be done much better by the GPU (having a > look in the world of gaming, where some "super-mega-ultra-antialiasing" is > done with more than 100 frames per seconds in highest resolutions.
Before going to the GPU, I would look if the MapServer resampling code couldn't already be optimized on the CPU. There's likely room for improvements. > Now there is an option to get some new servers with integrated GPUs (Nvidia > GTX1080) and asked myself (and now the community ;-) ) whether it would > make sense to exercise that option... What is not obvious performance wise is that you would need to transfer buffers back and forth between the CPU and GPU. Even -- Spatialys - Geospatial professional services http://www.spatialys.com
_______________________________________________ mapserver-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapserver-users
