in reply to Using large result sets from a database

You could use a cache (like Squid) to keep already issued pages for a while. This will keep the load from your webserver.

Be sure to only cache the results of the large result heap, and not the pages you want to be interactively, or be sure there is a state variable in your CGI-string.

Another way would be to create a view in the database with the results, adding a sequential numbering. Use that numbering to fetch a slice of the data.

Hope this helps,

Jeroen
"We are not alone"(FZ)

  • Comment on Re: Using large result sets from a database