Cameron Shorter wrote: > As part of our robustness testing of AWDIP deployments of Geoserver > (which includes Community Schemas), we have signed up to do "White box > testing". Ie, work out what is happening inside Geoserver for the AWDIP > use cases. > The end goal is to identify areas in the code where performance can be > improved. > > To this end, Stefan has started setting up profiling for Community > Schema deploys of Geoserver. Unfortunately we have a limited budget for > this and so we are looking for the 80% wins from 20% effort. > > So what I'm interested to hear are suggestions as to what parts of the > code we should focus on. > - Generating the capabilities document - WMS Rendering speed is a good test; it manages to abuse just about everything. - Straight up requesting Features based on BBox is good
Is this the kind of thing you had in mind? It matches the kind of activites uDig depends on :-) Remember if you are actually testing community schema to make use of: - When rendering WMS compare simple attribtues, vs styles that refer to nested attributes - wfs requests that included all attributes, vs only some attribtues > We will be collating the results of our tests here: > https://extranet.lisasoft.com/wiki/index.php/AWDIP_Software_Test_Results#Observations_from_White_Box_Testing > Have fun, Jody ------------------------------------------------------------------------- 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
