Improve rendered layer setup performance

Description

Rendered layer setup from a Context definition is slow. Use a profiler to detect where the time is spent.

One possible item is to avoid Style2D object proliferation by recognizing common situation in which the same style (or a limited
number of styles) are generated for most features in a layer, maybe by adding a "getMultiplicity" method on symbolizers to know in advance the maximum number of styles that could be generated.

Another item is to avoid cloining by avoiding the building of "frozen" geometries.

Yet another, visible on style change, is to move the geometry proxy map onto the RenderedLayerFactory so that the map is not lost if
a layer is replaced with another as a result of styiling change.

More suggestions welcomed

Environment

None

Activity

Show:
codehaus
April 10, 2015, 2:57 PM

CodeHaus Comment From: aaime - Time: Wed, 10 Mar 2004 14:23:18 -0600
---------------------
Most of the above issues have already been resolved. To get more

we need to:

  • generate a layer of rendered marks when possible

  • have data source read only the needed attributes so that

  we can read the geometries only one time and only the

  needed attributes after the first data loading.

codehaus
April 10, 2015, 2:57 PM

CodeHaus Comment From: aaime - Time: Sat, 19 Aug 2006 02:27:43 -0500
---------------------
The old J2DRenderer is retired and will be replaced by a new one when Martin has time to work on it, so closing this optimization attempt. Will see how the new one fares and work on it.

Assignee

Unassigned

Reporter

codehaus

Triage

None

Components

Fix versions

Affects versions

Priority

Medium
Configure