[Typo3-dev] RealURL : high server load and optimization

Ries van Twisk typo3 at rvt.dds.nl
Mon Oct 17 22:26:53 CEST 2005


Jan-Erik Revsbech wrote:

>>I am currently writing a little BE module that hooks into one of the
>>*SELECT* functions in class.t3lib_db.php
>>I am going to log all select to the DB and see  what  'where' clauses
>>are used mostly and doign index optimalisations
>>based on these statistics...
>>
>>any thought about that?
>>
>>    
>>
>
>You could also just turn on the slow queries log in MySQL, it has an option 
>to log all queries which are not using an index.
>
>I have done what you suggest above (making DBAL log queires which run 
>slowly) and generelly find that TYPO3 is well optimized in most cases (there 
>are some exceptions, but mostly with extension).  One (as I see it) big 
>problem is the comma seperated list, which are not easyly indexed. Having 
>20.000+ be_users nested into groups make a *lot* of slow queries due to the 
>comma list used to associate groups with their parent group. There is really 
>something to gain here, but only if you have many be_users. As I understand 
>the patch for 4.0 which enables nested fe_groups also uses comma lists, 
>which might affect large sites with nested groups.
>
>  
>
Jan,

any change to share the code?
I don't know to much about logging slow queries on mysql but as far as
I know the 4.1 version only log's queries that are slow (in time) which 
renders that function useless.

Since I don't have mysql 5.x installed I cannot see queries that don't 
use indexes... properly you have?

Still,
I am really curious about it and see if we can optimze the indexes 
afterall, it's not only typo3 core but also all
extentions that needs some tuning...

Ries








More information about the TYPO3-dev mailing list