Hello List,
I have a question about two new Oracle NG Datastore properties where I
didn,t find documentation.
In the new Oracle NG Datastore there are the connection timeout property.
What kind of units there will be used? I think milliseconds but I'm not
realy sure about it.
And what is the meening of connection timeout? The timeout to get a
connection to the Oracle DB?
Secound is the fetch size property.
There I have the same questions. What kind of units will be used there? I
think kb.
And what is the meening of fetch size? The size in kb which will be posted
from the geoserver to the DB?
Sorry about this simple questions but I have search on many places and there
wasn't any answer about this questions.
Thx 2StepForward
--
View this message in context: http://www.nabble.com/Oracle-NG-Datastore%2C-connection-timeout-and-fetch-size-tp23403792p23403792.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
2StepForward ha scritto:
Hello List,
I have a question about two new Oracle NG Datastore properties where I
didn,t find documentation.
In the new Oracle NG Datastore there are the connection timeout property.
What kind of units there will be used? I think milliseconds but I'm not
realy sure about it.
And what is the meening of connection timeout? The timeout to get a
connection to the Oracle DB?
Yes, but the unit is seconds, not milliseconds.
Secound is the fetch size property.
There I have the same questions. What kind of units will be used there? I
think kb.
And what is the meening of fetch size? The size in kb which will be posted
from the geoserver to the DB?
Nope, it's the number of records that will be pulled in one network
transfer from Oracle to GeoServer while reading.
Too low (less than 50) and you'll suffer from network latency, too high
and you risk pushing GeoServer towards an out of memory error because it
will have to keep that batch of records in memory while turning them
into GeoTools features that can be used in the rest of the GeoServer
processing chain.
I've updated the documentation accordingly, you'll be able to find
it in tomorrow's nightly build of the docs
(http://gridlock.openplans.org/geoserver/1.7.x/doc/)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Hi Andrea,
thanks for fast reply. These properties are nice things to configure the DB
connection.
Best regards 2StepForward
Andrea Aime-4 wrote:
2StepForward ha scritto:
Hello List,
I have a question about two new Oracle NG Datastore properties where I
didn,t find documentation.
In the new Oracle NG Datastore there are the connection timeout property.
What kind of units there will be used? I think milliseconds but I'm not
realy sure about it.
And what is the meening of connection timeout? The timeout to get a
connection to the Oracle DB?
Yes, but the unit is seconds, not milliseconds.
Secound is the fetch size property.
There I have the same questions. What kind of units will be used there? I
think kb.
And what is the meening of fetch size? The size in kb which will be
posted
from the geoserver to the DB?
Nope, it's the number of records that will be pulled in one network
transfer from Oracle to GeoServer while reading.
Too low (less than 50) and you'll suffer from network latency, too high
and you risk pushing GeoServer towards an out of memory error because it
will have to keep that batch of records in memory while turning them
into GeoTools features that can be used in the rest of the GeoServer
processing chain.
I've updated the documentation accordingly, you'll be able to find
it in tomorrow's nightly build of the docs
(http://gridlock.openplans.org/geoserver/1.7.x/doc/)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
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/Oracle-NG-Datastore%2C-connection-timeout-and-fetch-size-tp23403792p23405194.html
Sent from the GeoServer - User mailing list archive at Nabble.com.