Does the data change often? If not you could just enable query cache and
cache connection threads and you'd probably be fine.
Dan wrote:
After thinking about this a while I also thought of making my own
cache. The problem with that is would it be any faster or have any
less strain on the server than having multiple requests/connections to
the database?
- Dan
"Per Jessen" <per@xxxxxxxxxxxx> wrote in message
news:fe11ig$k5t$1@xxxxxxxxxxxxxxxxxxx
Dan wrote:
I need to retrieve a huge amount of data form a database and do so
many times. To eliminate the overhead of connecting to the database
and pulling down all that info over and over, I'm trying to pull it
down only once and stick it into a session. The problem is I get the
first few results and everything works fine. But then after those
first 5 or so I only get 0's. My first thought is that this is because
of a limit on memory that sessions can take up or file size/space
where the sessions are stored. I looked in the PHP.INI and I didn't
find anything though.
Any ideas on how to fix this problem or a more elegant solution to my
huge data needs?
IF there is a problem in using session storage, you could just use your
own file cache instead.
Or you could the database query cache, depending on how much data you're
talking about.
/Per Jessen, Zürich
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
