First of all, is performance an issue? If the answer is no, then (as with all optimization questions) don't do it.
Secondly if performance is an issue, have you tried using mod_perl and relatives to speed things up? Until you have tried the obvious performance boosters, don't go for any changes that will complicate your code.
But if you have done the above two, and performance is an issue, then it is valid to cache data in files to move load off of the database. However doing that introduces many new complications that can go wrong.
All that said, if this issue concerns you, you can do something right now to make this easier. Isolate the call to get data into a single subroutine. If you have multiple scripts, move that routine into a module and call it from the scripts. This takes little work to do, is good for your code quality, and means that if this ever does become a problem, you will be able to retrofit any design you want onto the existing system quite easily.
In reply to Re (tilly) 1: Technique Efficiancy
by tilly
in thread Technique Efficiancy
by Monolith-0
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |