Yes the db server and the webserver are on the same box, local
connections are much faster than network ones according to mysql.  When
the site is busy the percent of the system being used by mysql and that
being used by PHP/Apache, I estemate would be around 90%-10% so if I get
the db load down I'll have smooth sailing.

I'm not attempting to elimate the compalition of PHP, I just want to
eliminate some database queries.  I don't particually care for the idea
if writing static html files. I've had really bad experiences with stale
files our old system.

The way I'm exploring now is to build a caching layer between the php
application and mysql.

I want the app to query the caching layer just about the same way it
queries the database, but add a few other details, time to live, cache
name etc.  The caching layer will check to see if the query is cached,
make sure it's not expired, and return the data just like a result set
from the db query.  If it is expired, or doesn't exist then it will
query and create the cache file for next time.

I'm leaning toward storing the data in XML, and kicking around the idea
of storing it on a ram disk so it would have killer fast access time.

I expected to get tons of links to libraries or other apps that have
data caching, I'm quite supprised that I haven't yet.

On Mon, 2002-01-21 at 14:20, DL Neil wrote:

> 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?
Jeff Bearer, RHCE

PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to