An observation that we have found when using app schema, is that it can be quite slow (5 second responses versus 200 millisecond for simple features). We've looked at the database SQL queries that app schema produces, and it appears that there are two queries being produced:
1. The first query extracts all the data from a given table (e.g. select * from table) WITHOUT any SQL where clause. 2. For each record found, another query is run select data from the database. It's the first query that is slow. It appears that filtering is done in memory through Java rather than using SQL where clauses. This approach is fine for small datasets, but when you get large datasets (we have 300,000 records) you have a relatively slow WFS. Is there any way to trigger use of SQL where clauses in app schema? Maybe we've just set up our workspace/mappings wrong. Cheers, Andrew Betlehem ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
