geowolf wrote > Have no idea there, haven't used sql server in months. > This would require some investigation inside the code, but I have no time > to do that right now > outside of working hours.
Today I did all kinds of tests: - Created 2 layers from scratch to verify it had nothing to do with copying the data directory (as with the data store issue) - using other geoserver versions - changing request version (1.1.0 / 1.0.0) - changing output format (gml2, json) Since this afternoon this issue isn't reproducable anymore. And I have totally no idea why these queries aren't generated anymore. Yesterday and this morning a request took 20 seconds, now it takes 600-1000ms (and the complete table query isn't executed anymore). Completely flabbergasted! -- View this message in context: http://osgeo-org.1560.x6.nabble.com/GetFeature-request-extremely-slow-after-upgrade-to-GeoServer-2-3-3-tp5067365p5067656.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
