Rob Atkinson wrote: > 3) The database seems to be hit twice per query, which may be a > significant overhead if the db side is slow
That was one thing I discovered when profiling the AWDIP Geoserver yesterday. I talked with Andrea about that and he explained to me that this is necessary to get the number of features and is also done in the "normal" Geoserver. However, there some ways to improve the performance in this point (e.g. done in the postgis datastore). Have such improvements been implemented for the community module? I also discovered that the function org.geotools.feature.Name.getURI() is called very, very often in an AWDIP Geoserver (not that often in a normal Geoserver). Each time it is called a StringBuffer-object is created, one string appended and then the content of the buffer is returned by the function as String. Since this function is used that frequently, it might be worth to do some tuning here. Maybe it's possible to store the return value in a variable to use it later, if the function is called on the same objects. Or maybe at least the StringBuffer object can be reused. cheers, stefan -- Stefan Hansen Software Engineer LISAsoft --------------------------------------------------- Ph: +61 3 8680 3200 Fax: +61 3 8680 3299 Mob: +61 Level 9, 601 Bourke St, Melbourne Vic 3000 --------------------------------------------------- LISAsoft is part of the A2end Group of Companies http://www.ardec.com.au http://www.lisasoft.com http://www.terrapages.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
