[Geoserver-users] Geoserver with ArcSDE slow render performance

GeoServer GeoServer User
1

Hi,

I am using geoserver 1.7rc1 with arcSDE 9.1 and have configured geoserver
such that a layer from our arcSDE displays in the demo preview "Mini-map
preview of the enabled FeatureTypes".

The problem is that rendering the layer is slow - about 8 seconds. Zoom in
- 8 sec, pan - 8 sec etc.

The featureType configuration has cache enabled with cache time of 50000,
but this only helps if I zoom out, after zooming in.

I have geoserver installed on my pc, arcsde is on another server on the
local network. Using arcCatalogue to preview the same layer in arcSDE is
nice and quick.

How can I make the geoserver/arcSDE combination perform better?

Thanks in advance

Mark
--
View this message in context: http://www.nabble.com/Geoserver-with-ArcSDE-slow-render-performance-tp19025666p19025666.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

Hi Mark,

that is strange, I found 1.7.x being faster than in previous releases, and the
difference being more evident when there are more than one arcsde layer in
the map context, since the new arcsde code makes a much more clever use of
connections.

Is your comparison with ArcMap response time being done from the same client
machine? or is the ArcMap instance being run on the same machine than the sde
server, or a faster network link, etc? Or may be ArcMap seems faster because
being a desktop app it draws stuff incrementally so it appears to start
sooner but actually takes a while to draw all the features?

I'm interested in this sort of performance problems but would need more
information in order to assess it. Did you tried using multiple tiles in the
openlayers map preview? does it make any difference?

how large and complex is your layer?

The more information you can provide the better I could help you.

Cheers,

Gabriel

On Monday 18 August 2008 12:38:08 am Mark9090 wrote:

Hi,

I am using geoserver 1.7rc1 with arcSDE 9.1 and have configured geoserver
such that a layer from our arcSDE displays in the demo preview "Mini-map
preview of the enabled FeatureTypes".

The problem is that rendering the layer is slow - about 8 seconds. Zoom in
- 8 sec, pan - 8 sec etc.

The featureType configuration has cache enabled with cache time of 50000,
but this only helps if I zoom out, after zooming in.

I have geoserver installed on my pc, arcsde is on another server on the
local network. Using arcCatalogue to preview the same layer in arcSDE is
nice and quick.

How can I make the geoserver/arcSDE combination perform better?

Thanks in advance

Mark

3

Thanks Gabriel,

I am using the arcCatalog client on the same PC as the geoserver
installation. So the problem with geoserver/arcSDE performance shouldn't be
network related or arcSDE server related.

The layer I am using is very simple - 12 points representing city locations.
I only tried a single tile option.

I am just trying the tiled option now and it takes at least 40 sec to render
when zooming in. Pan in tile mode doesn't re request images, caching seems
to be smarter. Changing back to single tile takes 8 seconds to render.
Weird. Could it be that connections aren't pooling and are instead being
recreated on each request and so taking longer then single tile mode?

I tried tiled mode on another layer (australia coastline) and it takes 2m15s
before the first tile appears; all tiles are done at 3min. Using single tile
mode on this layer takes 12 sec. I've attached metadata for the this layer
to give you some background info on the layer.

http://www.nabble.com/file/p19042456/aussiecoast.txt aussiecoast.txt

Using arcCatalog preview on the same layers is almost instantaneous.

Connection management seems to have some problems though, while in tiled
mode this error occurs sometimes, so I restart tomcat and start over:

Caused by: org.geotools.arcsde.pool.UnavailableArcSDEConnectionException:
The ma
ximun of 3 to org.geotools.arcsde.pool.ArcSDEConnectionConfig[dbtype=arcsde,
ser
ver=*****, port=5151, instance=sde, user=sde_viewer, password=*****,
minConnections=6, maxConnections=10, connTimeOut=50000] has been reached
        at
org.geotools.arcsde.pool.SessionPool.getSession(SessionPool.java:299)

I'm keen to work this out so let me know what else I can do or information I
can supply.

Thanks

mark

Gabriel Roldán-5 wrote:

Hi Mark,

that is strange, I found 1.7.x being faster than in previous releases, and
the
difference being more evident when there are more than one arcsde layer in
the map context, since the new arcsde code makes a much more clever use of
connections.

Is your comparison with ArcMap response time being done from the same
client
machine? or is the ArcMap instance being run on the same machine than the
sde
server, or a faster network link, etc? Or may be ArcMap seems faster
because
being a desktop app it draws stuff incrementally so it appears to start
sooner but actually takes a while to draw all the features?

I'm interested in this sort of performance problems but would need more
information in order to assess it. Did you tried using multiple tiles in
the
openlayers map preview? does it make any difference?

how large and complex is your layer?

The more information you can provide the better I could help you.

Cheers,

Gabriel

On Monday 18 August 2008 12:38:08 am Mark9090 wrote:

Hi,

I am using geoserver 1.7rc1 with arcSDE 9.1 and have configured geoserver
such that a layer from our arcSDE displays in the demo preview "Mini-map
preview of the enabled FeatureTypes".

The problem is that rendering the layer is slow - about 8 seconds. Zoom
in
- 8 sec, pan - 8 sec etc.

The featureType configuration has cache enabled with cache time of 50000,
but this only helps if I zoom out, after zooming in.

I have geoserver installed on my pc, arcsde is on another server on the
local network. Using arcCatalogue to preview the same layer in arcSDE is
nice and quick.

How can I make the geoserver/arcSDE combination perform better?

Thanks in advance

Mark

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/Geoserver-with-ArcSDE-slow-render-performance-tp19025666p19042456.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

4

ArcSDE has quite a limited number of allowed non-ESRI client
connections. I wonder if the number of connections Geoserver is trying
to set-up is high enough to trigger a bit of a failure storm that
slows everything to a crawl. Try setting your max connections to 3
and min to 1.

The other thing I think when I hear about inexplicable speed issues is
name resolution -- when one resolution method fails, but takes a
looooong time to time-out, and then a second method succeeds. Using an
IP address instead of a server host name is a quick way to check this
out.

On Mon, Aug 18, 2008 at 6:23 PM, Mark9090 <mrehbein@anonymised.com> wrote:

Thanks Gabriel,

I am using the arcCatalog client on the same PC as the geoserver
installation. So the problem with geoserver/arcSDE performance shouldn't be
network related or arcSDE server related.

The layer I am using is very simple - 12 points representing city locations.
I only tried a single tile option.

I am just trying the tiled option now and it takes at least 40 sec to render
when zooming in. Pan in tile mode doesn't re request images, caching seems
to be smarter. Changing back to single tile takes 8 seconds to render.
Weird. Could it be that connections aren't pooling and are instead being
recreated on each request and so taking longer then single tile mode?

I tried tiled mode on another layer (australia coastline) and it takes 2m15s
before the first tile appears; all tiles are done at 3min. Using single tile
mode on this layer takes 12 sec. I've attached metadata for the this layer
to give you some background info on the layer.

http://www.nabble.com/file/p19042456/aussiecoast.txt aussiecoast.txt

Using arcCatalog preview on the same layers is almost instantaneous.

Connection management seems to have some problems though, while in tiled
mode this error occurs sometimes, so I restart tomcat and start over:

Caused by: org.geotools.arcsde.pool.UnavailableArcSDEConnectionException:
The ma
ximun of 3 to org.geotools.arcsde.pool.ArcSDEConnectionConfig[dbtype=arcsde,
ser
ver=*****, port=5151, instance=sde, user=sde_viewer, password=*****,
minConnections=6, maxConnections=10, connTimeOut=50000] has been reached
       at
org.geotools.arcsde.pool.SessionPool.getSession(SessionPool.java:299)

I'm keen to work this out so let me know what else I can do or information I
can supply.

Thanks

mark

Gabriel Roldán-5 wrote:

Hi Mark,

that is strange, I found 1.7.x being faster than in previous releases, and
the
difference being more evident when there are more than one arcsde layer in
the map context, since the new arcsde code makes a much more clever use of
connections.

Is your comparison with ArcMap response time being done from the same
client
machine? or is the ArcMap instance being run on the same machine than the
sde
server, or a faster network link, etc? Or may be ArcMap seems faster
because
being a desktop app it draws stuff incrementally so it appears to start
sooner but actually takes a while to draw all the features?

I'm interested in this sort of performance problems but would need more
information in order to assess it. Did you tried using multiple tiles in
the
openlayers map preview? does it make any difference?

how large and complex is your layer?

The more information you can provide the better I could help you.

Cheers,

Gabriel

On Monday 18 August 2008 12:38:08 am Mark9090 wrote:

Hi,

I am using geoserver 1.7rc1 with arcSDE 9.1 and have configured geoserver
such that a layer from our arcSDE displays in the demo preview "Mini-map
preview of the enabled FeatureTypes".

The problem is that rendering the layer is slow - about 8 seconds. Zoom
in
- 8 sec, pan - 8 sec etc.

The featureType configuration has cache enabled with cache time of 50000,
but this only helps if I zoom out, after zooming in.

I have geoserver installed on my pc, arcsde is on another server on the
local network. Using arcCatalogue to preview the same layer in arcSDE is
nice and quick.

How can I make the geoserver/arcSDE combination perform better?

Thanks in advance

Mark

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
View this message in context: http://www.nabble.com/Geoserver-with-ArcSDE-slow-render-performance-tp19025666p19042456.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

5

Thanks Paul,

Good suggestions.

I lowered the connections to 1 and 3. I also used the IP of the arcSDE
server in the connection details and restarted tomcat. For "single tile"
mode the time to render didn't change. For "tiled" mode it will render some
of the tiles but others will fail and the following error occur which isn't
surprising since it takes so long to render and release the connection.
Rendering is still slow, 35s before first tile appears and so on. This
seems a little faster then previously, however I've decreased the
connTimeOut from 50000 to 5000.

This shows what the render looks like:
http://www.nabble.com/file/p19044643/geoserver.png geoserver.png

This is the error.

Caused by: org.geotools.arcsde.pool.UnavailableArcSDEConnectionException:
The ma
ximun of 0 to org.geotools.arcsde.pool.ArcSDEConnectionConfig[dbtype=arcsde,
ser
ver=*****, port=5151, instance=sde, user=sde_viewer, password=*****, minCo
nnections=1, maxConnections=3, connTimeOut=5000] has been reached
        at
org.geotools.arcsde.pool.SessionPool.getSession(SessionPool.java:299)

Paul Ramsey-3 wrote:

ArcSDE has quite a limited number of allowed non-ESRI client
connections. I wonder if the number of connections Geoserver is trying
to set-up is high enough to trigger a bit of a failure storm that
slows everything to a crawl. Try setting your max connections to 3
and min to 1.

The other thing I think when I hear about inexplicable speed issues is
name resolution -- when one resolution method fails, but takes a
looooong time to time-out, and then a second method succeeds. Using an
IP address instead of a server host name is a quick way to check this
out.

--
View this message in context: http://www.nabble.com/Geoserver-with-ArcSDE-slow-render-performance-tp19025666p19044643.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

6

Hi,

I've worked out how to turn on verbose logging. Below is the log for a
request that takes 7 seconds to render a layer with 12 points:

http://www.nabble.com/file/p19044996/geoserver.log geoserver.log

The 7 second response is taken up in between these two log entries, which
corresponds to the first use of an arcSDE connection for this request. The
next two uses of an arcSDE connection during this request are very quick:

2008-08-19 16:09:33,764 DEBUG [arcsde.pool] - -->Session[5] out of
connection pool. Active: 1, idle: 0
2008-08-19 16:09:40,483 TRACE [arcsde.pool] - passivating connection
Session[5]

This information should help a lot more.

Thanks

Mark

--
View this message in context: http://www.nabble.com/Geoserver-with-ArcSDE-slow-render-performance-tp19025666p19044996.html
Sent from the GeoServer - User mailing list archive at Nabble.com.