CMS / System Resource question?

[eluser]mddd[/eluser]
Mischievous, I didn't mean that you should put the values in a file instead of in the database.
I meant that you should store it in the database, but then cache it. If you do queries that give the same results every time (like getting some setting from the database that doesn't change often), you save the results of the query to a file. When an administrator changes the value (through a cms, I would guess?) you make sure you throw away that file.
In your application, when you need to get the variable you first try to get it from the file. If the file does not exist, get it from the database and save it to the file so next time you won't have to go to the database.
I haven't looked into the cache library n0xie points to, but I'm sure that does pretty much the same as I just decribed. So yes, definitely check it out. I will too