On Tue, Sep 16, 2014 at 2:17 PM, Jody Garnett <[email protected]>
wrote:
> This is the first we have heard of it Jakob, I am not aware of any change
> that would be causing your speed regression.
>
> Can you reproduce this performance difference with the default data
> directory? Or is it something specific to using PostGIS?
>
> One thing to keep an eye out for is new functionality that the developers
> consider stable that is off by default in 2.5.x. As an example we have
> changed scale calculations, they are available in 2.5.x series - but used
> as the default in 2.6.x.
>
>
Clarification needed here, we did not change the way we do scale
computations, we added a parameter to allow the user
to control the way we do it, but the default is the same method as before
(unless we have bugs there)
> I could easily see a change in scale calculation changing the amount of
> data your rules draw at a given zoom level - resulting in a performance
> regression.
>
>
True, however the change will also be pretty visible, as you won't get the
same map in the output. Jacob, do you see changes in the generated map?
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
