I have had time to test a little more, and here is what i found out - the pictures look (exactly) the same. Picture size differs just a little (2.5.2: 2264928 byte 2.6 rc1: 2265587 byte).
- when plugging in tomcat against Java visual vm, i found out, that there was a class org.postgresql.core.visiblebufferedinputstream.readmore() that consumed significantly more cpu in all test cases in 2.6. (Typically for a test case 2.6 40.7 % / 2.5.2 13.7 %) - in PostGIS: -- turned on logging for sql queries -- did same wms getmap from 2.5.2 and 2.6rc1 --> turned out, that in 2.6, first the query below was executed 773 times (took 2.316 seconds) and then again between each SELECT geometry. This makes the queries in PostGIS take about 3 times longer for 2.6 than 2.5.2. The query that is executed in PostGIS when using 2.6: (this query returns the information about the tables in the schema): Here is a LINK <https://drive.google.com/file/d/0B-5GTVFPLqxUQjltUXVGZ1ZiWXM/edit?usp=sharing> to the complete postgresql log using 2.5.2 and here is a LINK <https://drive.google.com/file/d/0B-5GTVFPLqxUTXRRaUpGUTduZVU/edit?usp=sharing> to the complete log using 2.6. SELECT NULL AS TABLE_CAT, n.nspname AS TABLE_SCHEM, c.relname AS TABLE_NAME, CASE n.nspname ~ '^pg_' OR n.nspname = 'information_schema' WHEN true THEN CASE WHEN n.nspname = 'pg_catalog' OR n.nspname = 'information_schema' THEN CASE c.relkind WHEN 'r' THEN 'SYSTEM TABLE' WHEN 'v' THEN 'SYSTEM VIEW' WHEN 'i' THEN 'SYSTEM INDEX' ELSE NULL END WHEN n.nspname = 'pg_toast' THEN CASE c.relkind WHEN 'r' THEN 'SYSTEM TOAST TABLE' WHEN 'i' THEN 'SYSTEM TOAST INDEX' ELSE NULL END ELSE CASE c.relkind WHEN 'r' THEN 'TEMPORARY TABLE' WHEN 'i' THEN 'TEMPORARY INDEX' ELSE NULL END END WHEN false THEN CASE c.relkind WHEN 'r' THEN 'TABLE' WHEN 'i' THEN 'INDEX' WHEN 'S' THEN 'SEQUENCE' WHEN 'v' THEN 'VIEW' ELSE NULL END ELSE NULL END AS TABLE_TYPE, d.description AS REMARKS FROM pg_catalog.pg_namespace n, pg_catalog.pg_class c LEFT JOIN pg_catalog.pg_description d ON (c.oid = d.objoid AND d.objsubid = 0) LEFT JOIN pg_catalog.pg_class dc ON (d.classoid=dc.oid AND dc.relname='pg_class') LEFT JOIN pg_catalog.pg_namespace dn ON (dn.oid=dc.relnamespace AND dn.nspname='pg_catalog') WHERE c.relnamespace = n.oid AND n.nspname LIKE 'public' AND c.relname LIKE '%' AND (false OR ( c.relkind = 'r' AND n.nspname !~ '^pg_' AND n.nspname <> 'information_schema' ) OR ( c.relkind = 'v' AND n.nspname <> 'pg_catalog' AND n.nspname <> 'information_schema' ) ) ORDER BY TABLE_TYPE,TABLE_SCHEM,TABLE_NAME Any ideas what may cause this? best regards, Jakob -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Geoserver-2-6-RC1-slow-WMS-tp5161306p5164275.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
