hello martin,
thanks for your quick response!!
>I will re-run again and check peak JVM heap usage before/after and >bring it up on the development list.
with 115000 big data objects and fetchSize=0 (=default behavoir=without cursor) 97% memory of my jboss system was used (jboss with -Xmx512m) during the select. with fetchsize=1 it was just 48%
>Do you see any drawbacks of an OJB-global default of fetchSize=1
>for PostgreSQL?
>Since this is on an OJB global level for PostgreSQL I guess that "1" might
>be too low to strike a balance between network traffic and memory consumption?
>It might be possible to use fetch size 1 explicitly only for iterators,
yes, even with an iterator, a fetchSize of '1' would be to low in generell. it's hard to find the best setting, but I guess '1000' would be better than '0'.
it would be great, if the fetchSize could be set per query or broker.
>(This should not affect OJB proxy-prefetching-limit since that prefecthing >is done one layer above the PostgreSQL JDBC level.)
yes, I agree.
>I will bring the discussion up on the dev-list pointing to this thread >and see what concensus is with respect to memory footpring vs network >rraffic/JDBC overhead.
thank you very much!
andreas
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
