Hello again!

I ran your script, but eventually it didn't solve our problem. Response time to get into Edit mode is still very long. We have quite a lot (HTML) content . We use custom "Mandeeps Live" modules for this purpose - that's why there are LiveHtml_Content and LiveArticles_Article_Version in "TOP 10 disc usage" tables.

You can see other tables on the picture below:

Project is quite big - more than 125 portals (some of them have more than 1000 pages and / or news). 

 We've already done some analysis on the database - there were no "strange stuff" - only queries / procedures from DNN Core (for getting information about Tabs, Modules, TabModules, TabPermission etc..)..

Hello again!

 As i said - we've already done that and found out stored procedures that are "time consuming". They are all part of DNN core, so we think that modyfing them is not a good idea - or it is? We do not know where to start. We have problems with page load speed since the begining of our project. We've chosen community version of DNN for our project. Do you personally think that we should think about DotNetNuke Evoq Content? Is community (open source) version capable to handle such large and complex projects (more than 100 portals, a lot of content, users, roles, etc.). The only problem now is page load and edit mode speed (very slow - from 10 seconds and up).

 We've found your "Turbo scripts" some months ago, but eventually using them did not resolve our problem.

Thank you