[Geoserver-users] unpredictable ArcSDE behaviour

GeoServer GeoServer User
1

HI Gabriel,

Thank you for your reply.

I just tried the nightly build for the arcsde plugin (12 Apr 2008) and now I am able to create a new ArcSde layer based on a view. :wink:

Regarding the timing:
We have another version of geoserver (I am not sure what version, I will find out from Chris T and get back to you on that). When I call the layer on this version (using the same method and the layer itself is from the same arcSDE view/table), it took only less than one second (I cannot get the exact time sample).

I have also tried to change the global maximum number feature (maximum feature =2000 or 10000000) to see it there is a difference but there seems to be no correlation in that. In both of the cases, I still get the same amount of time to pull 100 features (PS: the 100 features is the initial setting provided by GAIA)

Maximum Feature = 2000
Result:
13 Apr 12:07:45 INFO [geoserver.filters] - "POST /geoserver163_sde080412/wfs" took 35859ms

Maximum Feature = 1000000
Result:
13 Apr 12:09:48 INFO [geoserver.filters] - "POST /geoserver163_sde080412/wfs" took 35958ms

Cheers, Dv

-----Original Message-----
From: Gabriel RoldƔn [mailto:groldan@anonymised.com]
Sent: Friday, 11 April 2008 5:58 PM
To: Deavi Purnomo
Cc: Andrea Aime; geoserver-users@lists.sourceforge.net; Chris Tweedie
Subject: Re: [Geoserver-users] unpredictable ArcSDE behaviour

Hi Deavi,

sorry for the late answer, and thanks Andrea for stepping in.

On Thursday 10 April 2008 03:04:38 am Deavi Purnomo wrote:

Hi Andrea,

Thank you for your reply.

I have just tried the geoserver1.6.3. and it was working (Please note that
the feature is created based on the ArcSDE table). Although I must say it
took a long time to extract 1000 features (118329ms).

okay, that's good (that it worked, I mean)... the time is horrible and makes
me think if for some reason we would be doing a full table scan to get the
bounds or something like that...
Before digging into that, can you confirm that table performs well with other
software? just to discard a screwed up spatial index and so.

By using the new geoserver1.6.3 and the new arcSDE extension plugin, I
found another issue with the ArcSDE layers. When I want to create a new
ArcSde layer based on a view it did not allow me to create one and gave me
the following error message:

you spotted a bug here. I've already found and fixed it. I'll send you a jar
by private mail for you to try out.

Cheers,

Gabriel

GeoServer - Exception

The following exception was thrown:

java.lang.IllegalArgumentException: ArcSDE registered views can't be
writable

From the error message, it seems to indicate that the "ArcSDE View" is the
issue. Is this correct?

Thank you again for your kind help.

Kind regards, Dv

-----Original Message-----
From: Andrea Aime [mailto:aaime@anonymised.com]
Sent: Wednesday, 9 April 2008 5:04 PM
To: Deavi Purnomo
Cc: geoserver-users@lists.sourceforge.net; Gabriel RoldƔn
Subject: Re: [Geoserver-users] unpredictable ArcSDE behaviour

Dv_LGATE ha scritto:
> Hi list,
>
>
>
> I have been having a similar issue with the SDE layers. Does anyone know
> why
>
> this happens? Please help.
>
>
>
> These are the things that I have tried:

Gabriel may provide better answers, but in the meantime, have you tried

out GeoServer 1.6.3 and the associated ArcSDE extensions?

It should have quite a bit of significant ArcSDE improvements.

(oh, rememeber you have to grab the extension distributed with 1.6.3,

the older ones won't work, extensions datastores do work only with

the geoserver version they are built for).

Cheers

Andrea

This e-mail and any files transmitted with it are intended only for the use
of the addressee(s). It may contain information that is confidential and
privileged, in which case neither is intended to be waived or lost by
mistaken delivery to you. If you are not an intended recipient, any use,
interference with, disclosure, distribution or copying of this material is
unauthorised and prohibited. If you receive this e-mail in error, please
notify the sender by return e-mail and delete the message and any
attachments from your system. Unless specifically indicated, this e-mail
does not constitute formal advice or commitment by the sender or the
Western Australian Land Information Authority (Landgate). Information in
this message not relating to the official business of Landgate shall be
understood as neither given nor endorsed by it. It is your responsibility
to check any attachments for viruses and defects before opening or sending
them on. Landgate's liability is limited to re-supplying affected
attachments.

!DSPAM:4045,47fd67b1108446491211187!

2

Hi Grabriel,

I forgot to mention, just in case this is important, that the time sample that I stated below is based on Gaia 2ā€™s previewing the layer.

Cheers Dv

From: Deavi Purnomo
Sent: Sun 13/04/2008 11:53 AM
To: ā€˜Gabriel RoldĆ”nā€™
Cc: Andrea Aime; geoserver-users@lists.sourceforge.net; Chris Tweedie
Subject: RE: [Geoserver-users] unpredictable ArcSDE behaviour

HI Gabriel,

Thank you for your reply.

I just tried the nightly build for the arcsde plugin (12 Apr 2008) and now I am able to create a new ArcSde layer based on a view. :wink:

Regarding the timing:
We have another version of geoserver (I am not sure what version, I will find out from Chris T and get back to you on that). When I call the layer on this version (using the same method and the layer itself is from the same arcSDE view/table), it took only less than one second (I cannot get the exact time sample).

I have also tried to change the global maximum number feature (maximum feature =2000 or 10000000) to see it there is a difference but there seems to be no correlation in that. In both of the cases, I still get the same amount of time to pull 100 features (PS: the 100 features is the initial setting provided by GAIA)

Maximum Feature = 2000
Result:
13 Apr 12:07:45 INFO [geoserver.filters] - ā€œPOST /geoserver163_sde080412/wfsā€ took 35859ms

Maximum Feature = 1000000
Result:
13 Apr 12:09:48 INFO [geoserver.filters] - ā€œPOST /geoserver163_sde080412/wfsā€ took 35958ms

Cheers, Dv

-----Original Message-----
From: Gabriel RoldĆ”n [mailto:groldan@anonymised.comā€¦]
Sent: Friday, 11 April 2008 5:58 PM
To: Deavi Purnomo
Cc: Andrea Aime; geoserver-users@lists.sourceforge.net; Chris Tweedie
Subject: Re: [Geoserver-users] unpredictable ArcSDE behaviour

Hi Deavi,

sorry for the late answer, and thanks Andrea for stepping in.

On Thursday 10 April 2008 03:04:38 am Deavi Purnomo wrote:

Hi Andrea,

Thank you for your reply.

I have just tried the geoserver1.6.3. and it was working (Please note that
the feature is created based on the ArcSDE table). Although I must say it
took a long time to extract 1000 features (118329ms).
okay, thatā€™s good (that it worked, I mean)ā€¦ the time is horrible and makes
me think if for some reason we would be doing a full table scan to get the
bounds or something like thatā€¦
Before digging into that, can you confirm that table performs well with other
software? just to discard a screwed up spatial index and so.

By using the new geoserver1.6.3 and the new arcSDE extension plugin, I
found another issue with the ArcSDE layers. When I want to create a new
ArcSde layer based on a view it did not allow me to create one and gave me
the following error message:

you spotted a bug here. Iā€™ve already found and fixed it. Iā€™ll send you a jar
by private mail for you to try out.

Cheers,

Gabriel

GeoServer - Exception

The following exception was thrown:

java.lang.IllegalArgumentException: ArcSDE registered views canā€™t be
writable

From the error message, it seems to indicate that the ā€œArcSDE Viewā€ is the
issue. Is this correct?

Thank you again for your kind help.

Kind regards, Dv

-----Original Message-----
From: Andrea Aime [mailto:aaime@anonymised.com]
Sent: Wednesday, 9 April 2008 5:04 PM
To: Deavi Purnomo
Cc: geoserver-users@lists.sourceforge.net; Gabriel RoldƔn
Subject: Re: [Geoserver-users] unpredictable ArcSDE behaviour

Dv_LGATE ha scritto:

Hi list,

I have been having a similar issue with the SDE layers. Does anyone know
why

this happens? Please help.

These are the things that I have tried:

Gabriel may provide better answers, but in the meantime, have you tried

out GeoServer 1.6.3 and the associated ArcSDE extensions?

It should have quite a bit of significant ArcSDE improvements.

(oh, rememeber you have to grab the extension distributed with 1.6.3,

the older ones wonā€™t work, extensions datastores do work only with

the geoserver version they are built for).

Cheers

Andrea

This e-mail and any files transmitted with it are intended only for the use
of the addressee(s). It may contain information that is confidential and
privileged, in which case neither is intended to be waived or lost by
mistaken delivery to you. If you are not an intended recipient, any use,
interference with, disclosure, distribution or copying of this material is
unauthorised and prohibited. If you receive this e-mail in error, please
notify the sender by return e-mail and delete the message and any
attachments from your system. Unless specifically indicated, this e-mail
does not constitute formal advice or commitment by the sender or the
Western Australian Land Information Authority (Landgate). Information in
this message not relating to the official business of Landgate shall be
understood as neither given nor endorsed by it. It is your responsibility
to check any attachments for viruses and defects before opening or sending
them on. Landgateā€™s liability is limited to re-supplying affected
attachments.

!DSPAM:4045,47fd67b1108446491211187!

3

Hi,

Try rebuilding the spatial index, even if loading in other applications is fast [1].

I also had a speed problem rendering an SDE8.3/Oracle9.2 layer with GeoServer 1.6.0RC3. Retrieving a small amount of features (say 20) took over 30 seconds (Gabriel, remember talking about this at Girona?). The featureclass could be loaded quite fast in ArcMap, etc.

Playing with spatial grid sizes, I replaced the 1000 default with 3 levels (100, 1000 and 10000) and rebuilt the spatial index.
Now I get the same render 300x faster (< 100 ms for a 256px tile).
Not shure if changing grid size is necessary, or just re-creating the index is enough.
Anyway, setting an optimal grid size is a good practice.

Hope this helps.

[1] http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=Setting_spatial_indexes

Regards,

Oscar.

From: Deavi Purnomo
Sent: Sun 13/04/2008 11:53 AM
To: ā€˜Gabriel RoldĆ”nā€™
Cc: Andrea Aime; geoserver-users@lists.sourceforge.net; Chris Tweedie
Subject: RE: [Geoserver-users] unpredictable ArcSDE behaviour

HI Gabriel,

Thank you for your reply.

I just tried the nightly build for the arcsde plugin (12 Apr 2008) and now I am able to create a new ArcSde layer based on a view. :wink:

Regarding the timing:
We have another version of geoserver (I am not sure what version, I will find out from Chris T and get back to you on that). When I call the layer on this version (using the same method and the layer itself is from the same arcSDE view/table), it took only less than one second (I cannot get the exact time sample).

I have also tried to change the global maximum number feature (maximum feature =2000 or 10000000) to see it there is a difference but there seems to be no correlation in that. In both of the cases, I still get the same amount of time to pull 100 features (PS: the 100 features is the initial setting provided by GAIA)

Maximum Feature = 2000
Result:
13 Apr 12:07:45 INFO [geoserver.filters] - ā€œPOST /geoserver163_sde080412/wfsā€ took 35859ms

Maximum Feature = 1000000
Result:
13 Apr 12:09:48 INFO [geoserver.filters] - ā€œPOST /geoserver163_sde080412/wfsā€ took 35958ms

4

Hey Oscar,

sure, that may well be the root of the problem.
I'm a bit hands tied right now as I don't have a server reachable server with
enough bandwidth as to assess performance (ie, the low bandwidth is too much
a bottleneck).

Deavi could you follow Oscar's advise and report back your findings?

Cheers,

Gabriel

On Monday 14 April 2008 08:08:09 pm Oscar Fonts wrote:

Hi,

Try rebuilding the spatial index, even if loading in other applications is
fast [1].

<verbose>
I also had a speed problem rendering an SDE8.3/Oracle9.2 layer with
GeoServer 1.6.0RC3.
Retrieving a small amount of features (say 20) took over 30 seconds
(Gabriel, remember talking about this at Girona?).
The featureclass could be loaded quite fast in ArcMap, etc.

Playing with spatial grid sizes, I replaced the 1000 default with 3 levels
(100, 1000 and 10000) and rebuilt the spatial index.
Now I get the same render 300x faster (< 100 ms for a 256px tile).
Not shure if changing grid size is necessary, or just re-creating the index
is enough.
Anyway, setting an optimal grid size is a good practice.

Hope this helps.
</verbose>

[1]
http://webhelp.esri.com/arcgisdesktop/9.2/index.cfm?TopicName=Setting_spati
al_indexes

Regards,

Oscar.

------------------------------

> *From:* Deavi Purnomo
> *Sent:* Sun 13/04/2008 11:53 AM
> *To:* 'Gabriel RoldƔn'
> *Cc:* Andrea Aime; geoserver-users@lists.sourceforge.net; Chris Tweedie
> *Subject:* RE: [Geoserver-users] unpredictable ArcSDE behaviour
>
> HI Gabriel,
>
> Thank you for your reply.
>
> I just tried the nightly build for the arcsde plugin (12 Apr 2008) and
> now I am able to create a new ArcSde layer based on a view. :wink:
>
> Regarding the timing:
> We have another version of geoserver (I am not sure what version, I will
> find out from Chris T and get back to you on that). When I call the layer
> on this version (using the same method and the layer itself is from the
> same arcSDE view/table), it took only less than one second (I cannot get
> the exact time sample).
>
> I have also tried to change the global maximum number feature (maximum
> feature =2000 or 10000000) to see it there is a difference but there
> seems to be no correlation in that. In both of the cases, I still get the
> same amount of time to pull 100 features (PS: the 100 features is the
> initial setting provided by GAIA)
>
> Maximum Feature = 2000
> Result:
> 13 Apr 12:07:45 INFO [geoserver.filters] - "POST
> /geoserver163_sde080412/wfs" took 35859ms
>
> Maximum Feature = 1000000
> Result:
> 13 Apr 12:09:48 INFO [geoserver.filters] - "POST
> /geoserver163_sde080412/wfs" took 35958ms

!DSPAM:4045,48039d8e182495332866982!