Deathly slow query on a forum with a lot of posts.
Just commenting in such a topic, says nothing more other than someone wants to appear smarty. Include in your post what do you think as optimised query, and also be more specific on your meaning of "lot of posts", so the users can compare it with their forum's posts. So "Lot of posts" means 1000, 10000, 100000 or what?
And don't forget the saying: "If you don't have something good to say, is better to keep your mouth close".
Thank you and Merry Christmas to you and to your family.
Maria
Just commenting in such a topic, says nothing more other than someone wants to appear smarty. Include in your post what do you think as optimised query, and also be more specific on your meaning of "lot of posts", so the users can compare it with their forum's posts. So "Lot of posts" means 1000, 10000, 100000 or what?
In my case the forum has 2,162,154 posts and the query takes about 3-5 seconds. You could have clicked on the link to my forum to see the post total btw. I tried out the mod, found the query to be slow and removed it. I don't have time to optimize the query.
Quote:
And don't forget the saying: "If you don't have something good to say, is better to keep your mouth close".
This doesn't apply in this case. People need to know the good and the bad when it comes to these mods. An inexperienced forum owner could cripple his forum from installing something without considering the negative effects it could have on performance.
Quote:
Thank you and Merry Christmas to you and to your family.
Maria
In my case the forum has 2,162,154 posts and the query takes about 3-5 seconds. You could have clicked on the link to my forum to see the post total btw. I tried out the mod, found the query to be slow and removed it. I don't have time to optimize the query.
It's not about anount of posts my dear friend. It's about amount of users. The records in the parent table (in this case "Users"), is who takes more time and not the child table (in this case "Posts"). Simple because the child table is already indexed on userid, so the query stops running when userid is changing, unlike the parent table (users) where the query must go throughout all records.
In simple words: 1000 users X 2000 posts each, will take less time than 10000 users X 200 posts each, even if the total amount of posts is the same on both cases.
Quote:
Originally Posted by Boots
This doesn't apply in this case. People need to know the good and the bad when it comes to these mods. An inexperienced forum owner could cripple his forum from installing something without considering the negative effects it could have on performance.
Calorie wrote it somewhere. It's American saying, and yes I also disagree with it, but only in cases when someone says his opinion explaining it, just like you did in your second post.
Further to my other post about it recognising multiple usergroups, my installations doesn't seem to show users avatars, even though they DO have an avatar installed.
The top posters just has the default avatar showing.