Some more information: tests 1-3 were done with a in-house made software, which requested the layers with a random 3200x3200 m bounding box (same srs as data)
1) When requesting a single layer (road network, line sld) geoserver 2.6 rc1 and 2.5.2 are giving the response in similar time (my case 31 sec). 2) When requesting a layergroup (120 vector layers from PostGIS) at 1m /px resolution, 2.6 rc1 is almost 2 times slower (rc1: 172 seconds / 2.5.2: 94 seconds) 3) When requesting the same layergroup as in 2) but this time from another layergroup containing the layergroup in 2), 2.6 rc1 is much slower (rc1: 244 sec / 2.5.2: 94 seconds) When doing requests straight from the server on which geoserver is running (localhost:8080/geoserver...) both versions of geoserver delivers the requested map in same time (layergroup wiht 130 vector layers from PostGIS) Anybody having similar experiences? Ideas what I should look at? (Don't think this has anything to do with PNG encoding as I thought in previous post.) regards, Jakob -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Geoserver-2-6-RC1-slow-WMS-tp5161306p5162063.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
