Scott T. Hildreth wrote:
As Tim said, look at the RowCacheSize, I have seen big speed gains by increasing this attribute.
We do use that and I have also seen decent (maybe not big) gains. The big problem we have with it is maintaining a good setting as our data grows, since we usually set it to a number of rows. We also have seen some decent gains by pre-caching rows with one of the fetchall calls -- mostly in cases where the row processing in application space is long. Pre-caching allows us to get in and out of the database and close the connection, freeing up DB resources, then process the rows without consideration for the database over time. This seems to help eliminate rollback and "snapshot too old" errors in Oracle that we get with long running fetch/process cycles. The tradeoff, as with RowCacheSize, is a larger application process.
I would be interested to hear of other DBD::Oracle users' experiences with SELECTs that return very large result sets.
-- Steve Sapovits [EMAIL PROTECTED]
