Loading

Collabtive speed

General Discussion around Collabtive

Re: Collabtive speed

Postby ChristianF » 19.05.2015, 11:59

Hello,

You're welcome, and I'm glad I could help. :)

As for the subqueries (which is what "SELECT IN(SELECT...)" is called), they're not always the best solution. Most of the time you want to use JOINs, as subqueries can be quite inefficient as well. Haven't profiled the two methods on this function, so not quite sure what's the best approach here. Just used the subquery as that was the fastest to implement. ;)
I have planned on rewriting Collabtive further, to remove even more of the bottlenecks that are associated with the SQL queries. However, I'm not sure when I'll get it done. Time is scarce, and it requires rewriting a lot of the core functionality.

Considering the amount of data you had, I'm not surprised at the issues. As you've probably read in my other thread I've kind of expected that, considering the amount of extra queries per project/task is added. If we manage to get the number of queries down to 6-7 per pageload, instead of per task, you should experience a massive decrease in processing time.
Speaking of which, which is your average load time per page now?
ChristianF
 
Posts: 17
Joined: 13.03.2015, 10:18
Location: Norway

Previous

Return to General

Who is online

Users browsing this forum: No registered users

cron