Ok over the last few days here is the progress:
1) Text-Search-indexes of MySql indexing doesn't seem to speed things up...i.e....some of the modules...like CBB, Article using Text search for XOOPS Search.... seems to work much quicker from an id search...or an index of same information...then MySql Text index searching it...(still to try unique indexing more in concern of text information that needs quick access...yet current improvements stand we don't need this)
2) The XOOPS Session are a pain, again we have changed these ....trying to refine what the system uses and stores...as I feel XOOPS is heavy and this is one big part..(the other will explain)
We have this currently only indexing an ip address now as more work and more indexing is slower times...seems that we store a lot of information of users movements....that isn't needed to be indexed so much....
3) The Idea of putting Titles along with things is a daft one, numbers and letters sequentially used are ok and quicker...as the idea of an index is the fastest reference possible to get the data out of the table...
So in this case if a title or name is to be indexed, it must remain in it’s own index.....with the Id and what ever else is required ran as primary....so then the moment XOOPS looks for the data it knows where it goes, and what it is doing before it needs, goes a long way towards a more optimized Xoops.....
Explain that one...for instance....
A category ID is also linked to the topic ID....that is also a number for the page id for instance...these all go in primary as second fields....reason being otherwise it will look for these things each time they are asked for...that actually reduces server calls...yet adds index size...which if done well is then less load. by along way as it doesn’t have to stop and go where is this id that goes with that category before actually doing the said work of...data!....As last point that isn't indexed...and after saying Text-search-index isn't very good at referencing quicker then a normal index and a ID.....
The whole point of indexing is to save time looking for things in the information or data…..so when each template file, needs to know if it is displayed first and small points like that…accompanying these within the primary indexing…makes it that XOOPS has all needed references to run before…questioning the end data tables….instead it finds most of it in the index…and then doesn’t need to look in the data if done well…and depending what it is….
Yet on some occasions MySql is a database system
![](https://xoops.org/uploads/smil42e7a65fee35d.gif)
and with what we have been testing I am unsure if it is me and my web site runs better the system is cleaner….and many developers are following a blind donkey…as in it does appear people copied nuke…nuke had bad tables…and we have all followed this same methodology of placing things within MySql…
Could just be me, yet do feel that my site is running a load faster not heavy any more and can take much more….and considering it has a lot of module and a lot of data….then we definitely have gone a long way from Normal Xoops…