You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by "Galbreath, Mark" <Ga...@tessco.com> on 2002/09/06 19:16:03 UTC

RE: [DATA] Large result set iterations

ditto - stored procedure is just the ticket for this sort of problem.

-----Original Message-----
From: Bryan Hilterbrand [mailto:Bryan.Hilterbrand@bullwinkle.net]
Sent: Friday, September 06, 2002 11:55 AM

There are many potential solutions to this, but one is to figure out what
the end result of iterating through your result set is, then create a stored
procedure to do the same thing.

Bryan

----- Original Message -----
From: "Michael Lee" <ml...@hotmail.com>
Sent: Friday, September 06, 2002 9:42 AM

Hey, do any of you [FRIDAY] guys know how to handle iterating through
enourmously large result sets without storing the ResultSet object in
memory? I use JDBC cursors now but have to do the query upon each 'next' or
'previous'.

I always ask the tough questions that get few responses!
:)
Mike Lee

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: [DATA] Large result set iterations

Posted by Elderclei R Reami <re...@vertisnet.com.br>.
Hi all,

I've already came up with this question before. Actually, I think there is no definite solution to the problem. 
Several points must be analyzed before architecting it:

- number of users on normal hours
- number of users on peak hours
- whether the data change or do not change often
- whether the queries are often the same, or if they are very different each time
- available infrastructure
- what else?

For each combination of these parameters, there must be one almost best solution. For instance, I remember 
that I read a document about Altavista infrastructure and architecture. They've used lots of Digital machines with 
multi-Gigabytes of RAM, caches were running all around, and so on. Probably, they would show instantaneous 
response for queries like sex, java, web, and so on.

Analyze your problem variables, and you will reach a solution, that will not be the best for every case, but for 
most cases.

Cheers,
Elder

On Fri, 6 Sep 2002 13:16:03 -0400 , "Galbreath, Mark" <Ga...@tessco.com> escreveu :

> De: "Galbreath, Mark" <Ga...@tessco.com>
> Data: Fri, 6 Sep 2002 13:16:03 -0400 
> Para: 'Struts Users Mailing List' <st...@jakarta.apache.org>
> Assunto: RE: [DATA] Large result set iterations
> 
> ditto - stored procedure is just the ticket for this sort of problem.
> 
> -----Original Message-----
> From: Bryan Hilterbrand [mailto:Bryan.Hilterbrand@bullwinkle.net]
> Sent: Friday, September 06, 2002 11:55 AM
> 
> There are many potential solutions to this, but one is to figure out what
> the end result of iterating through your result set is, then create a stored
> procedure to do the same thing.
> 
> Bryan
> 
> ----- Original Message -----
> From: "Michael Lee" <ml...@hotmail.com>
> Sent: Friday, September 06, 2002 9:42 AM
> 
> Hey, do any of you [FRIDAY] guys know how to handle iterating through
> enourmously large result sets without storing the ResultSet object in
> memory? I use JDBC cursors now but have to do the query upon each 'next' or
> 'previous'.
> 
> I always ask the tough questions that get few responses!
> :)
> Mike Lee
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
> 
> 
> 
> 

Elderclei R Reami
Vertis Tecnologia
+55 11 3887-0835
www.vertisnet.com.br


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>