There's nothing to optimize on the database itself. Just poorly optimized queries and to fix those means fixing those queries.
CB has came a long way in that regard though. I've CB tested with 1 million user rows, 1 million activity posts, 1 million gallery entries, and 1 million groupjive categories and groups. GJ has a performance issue with category group counts. CB has a performance issue with userlists, but that was greatly improved already. CB Activity and CB Gallery seam to perform acceptable, but still some minor improvements that could be made. I've found a lot of slow queries are just Joomlas own fault primarily due to accessing ACL and not using an index and those queries have no static caching so our functions that access ACL do to stop duplicate slow queries.
Best way to find slow queries is to just turn on Joomlas debug mode so you can see the debug query log at the bottom and check the times there.
Kyle (Krileon)
Community Builder Team Member
Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums
CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
--
If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
--
If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
--
Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
--
My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
krileon
