optimized to do data processing as fast as possible, while CF is designed as
a web app language, that has some data processing facilities. Not to say
that running QofQs is slow, but using a DB will undoubtedly be faster on
large sets, because it can benefit from indexes and such, which CF doesn't
get to use.
-----Original Message-----
From: Lofback, Chris [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 11:24 AM
To: CF-Talk
Subject: RE: CF5: Oracle recordset via StoredProc and QofQ questions
So it's really just a question of RAM? No other serious performance
concerns for retrieving record sets via SP?
Thanks,
Chris
-----Original Message-----
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2003 12:08 PM
To: CF-Talk
Subject: Re: CF5: Oracle recordset via StoredProc and QofQ questions
Lofback, Chris wrote:
>
> 1) Are there any limitations/issues when retrieving large (say 250,000
rows of 10 varchar2(50) columns) recordsets from Oracle 8 using a stored
procedure? Is it slow? Unstable/flaky?
250,000 * 10 * 50 = 125 MB minimum
It needs to be stored in RAM.
> 2) Can QofQ handle a recordset that large?
If you have the RAM. Remember that with every QoQ you create a
new recordset that needs to be stored in RAM. Plus the output
page needs to be stored in RAM.
I would rethink and try to do more in the DB.
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
