11
Quote:
In my quest to save DB Queries, I was thinking maybe the XOOPS Config stuff like site name, description, etc should be stored in a php file rather than in the DB. This is needed for every page and calling it from a DB is kind of a waste.
Less DB queries = less page time gen.
Well you're right about the config: this precise point can be enhanced. It's not updated often, and the way it is retrieved made it one of the most messy part of the core: to reduce the number of queries settings have been organized by
frequency (several unrelated setttings are in the same group just because they are needed in all pages, so they can be retrieved using one single query).
Now, the
less DB queries assumption is not entirely accurate: RDBMS have been designed with scalability in mind. So, less DB queries may mean faster page generation on your own computer, but this may not work like this on a loaded server which has to process many simultaneous requests.
But anyway, you're looking in the good direction. However, this problem has already been thought of, and is one that inspired one of the most exciting new features I'll contribute to the new cores: in the future, settings will be programatically applied to core classes and scripts, generating
pre-configured code that will be used during page generation (it's a bit like offlining the entire config process, so it is not needed anymore in the runtime layer used by regular pages).
So don't waste your time here... whatever, if you want to remove useless queries there are other parts you can check (like the inefficient Smarty implementation generating one query for each included template...)
.
skalpa.>
Any intelligent fool can make things bigger, and more complex. It takes a touch of genius, a lot of courage, to move in the opposite direction.
Two things are infinite: the universe and human stupidity; and I'm not sure about the 1st one (A.Einstein)
