Here's the deal: if you are in a handling language (PHP/PERL, no matter), then you open a DBM table, then do a lookup, you pay for all that activity before you get the answer. The problem is that most page request handlers are not persistent, so they can't have always-open file handles... they must reopen for every call. This, of course, could be fixed by a persistent language like Python or any number of languages that will compile a shared object to hang off Apache, but that is WAY more complex than you need to go.
Ok it is not the language, it is apache itself. It is like coding with 1 arm tied behind ur back. It is a POS but it is the best POS out there

.
I will go back to my happy world where these problems do not exist

Ponders what would happen if u would take something allegroserve and then have a module which loads a shared library which is the PHP language.
That way u could install shit like wordpress etc on it.
Biggest problem is that allegroserve requires allegro lisp and that costs like $10K a bang. I wonder who thier clients, i think they must be military etc, because when i talked to a sales rep he did not really seem to be intrested in selling anything

With a system like that u fire up the lisp process. Then using something like slime and a secure shell you can compile and load code, that modifies even running programs.
But again it is outside this discussion

.