admin
Karma: 101
|
Re:OPTIMIZE the backend! - 2005/11/08 16:29
I beg your pardon, you are correct, and I take back my earlier statement. The admin side has been treated as having the lowest priority for efficiency, since there are fewer admins and they generally do less. So the order of optimisation is user side browsing, user side download, admin side.
But it has perhaps got a bit out of hand  It is acquiring information about containers that is the problem. Given the additional information provided in Remository 3.40 it would be difficult to devise a suitable join. However, I've implemented a buffering mechanism (which also exists in the Remository SEF software). So now all the container information is read from the database in one go and stored. Should be an acceptable memory overhead in pretty much all situations. The number of DB accesses is now down to less than the Mambo/Joomla ones.
The SQL you cite is actually constructing the select list of all possible containers. As it lists them complete with their full nested names, I'm not at all sure that a join would even be possible.
Thanks for bringing my attention to the issue.
Post edited by: admin, at: 2005/11/08 11:45
Martin Brampton aka Counterpoint
http://aliro.org
http://black-sheep-research.com |
Forum
