Re: How should I cache database data for php?
| From: | Richard Crawford | Date: | Mon, 21 Jan 2002 19:37:41 +0000 |
| Subject: | Re: How should I cache database data for php? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-81421@lists.php.net to get a copy of this message | ||
DL Neil wrote:
In which case, it seems to me that my solution would still be a good one. Reducing the number of hits on the database server by building static pages as needed to be served up by a web server would still reduce the load on the database server. -- Sliante, Richard S. Crawford mailto:rscrawford@mossroot.com http://www.mossroot.com AIM: Buffalo2K ICQ: 11646404 Yahoo!: rscrawford MSN: underpope@hotmail.com "It is only with the heart that we see rightly; what is essential is invisible to the eye." --Antoine de Saint Exupery "Push the button, Max!"er, yes and no! Jeff's original post mentioned reducing load on the db server - are the db and web servers on the same physical device - and thus his concern? - or perhaps if there are other apps needing to 'compete' with the web server to gain access to the db concurrently? =dnEven with straight HTML, a server's load capacity is not infinite. If my own server, an old Pentium with 4 GB of hard drive space, and which serves nothing but static HTML pages, got hit with more than a couple hundred hits in a short period of time, it would bomb. I must be misunderstanding your question. I've re-read your original post, and it seems to me that what you're trying to do is save webpage-bound database data in a way which will seriously reduce the load on a webserver; creating static HTML pages from database data instead of building pages dynamically when the user calls them would accomplish that goal, and that is what I was suggesting.You are right ;)