Re: [Geoserver-users] Slow or no start for large table

[Andrea A. <aa...@op...>]

Ugo Taddei wrote:
> Hello,
> 
> I have an oracle DB-based data store serving half a dozen layers/feature 
> types. One of the tables have >6000000 objects. When I config this 
> feature type using the GUI, I can get as far as the Demo and I'm able to 
>   see the features. (I have defined the bbox manually as the generate 
> button took ages.)
> 
> I then shut gs down, and try to restart it. It loads the other types, 
> but doesn't get past the one with the large table.
> 
> I can, however, see the features with udig. (It's there, it's indexed, 
> it's performing well.)
> 
> GS is 1.7.2. OS is Windows XP. DB is Oracle on Linux.
> 
> Does anyone have an idea about what's happening?

Yes, GeoServer is computing the native bbox on startup, doing the long
and expensive query that you avoided by putting in the bbox manually
in the UI.
The issue has been solved and 1.7.3 should not suffer from it anymore.
Please try out a GeoServer nightly build here:
http://gridlock.openplans.org/geoserver/1.7.x/

If possible use the oracle-ng datastore, that also has native support
for maxFeatures for the first time, which means your GetFeature
requests won't be stuck forever computing the bounding box (if you
enable the output of the feature collection bounding box in the
wfs configuratino, and set a maxFeature limit that avoids massive
data extractions).

Let us know how this works for you
Cheers
Andrea