Details
-
Bug
-
Status: Closed (View Workflow)
-
Resolution: Duplicate
-
3.0.0
-
None
-
None
-
PHP Environment:
Database:
Description
This is the error
!http://img233.imagevenue.com/loc569/th_49242_Untitled_122_569lo.jpg
and this the explanation and it has already being tested, is a bug, not something that should merely go to the support request forum
[quote= kevin_m1]
Any sql query that touches over 500,000 rows on a forum that has
380 posts, 18 members , 32 forums and is 3mb in size, MUST be some bad INNER / OUTER joins.
This will 100% certainly be causing a performance degrade also for people that do not have this limit in place (and server load averages will be increasing ! ) ... If the phpBB team do not commit this as a bug, then I fear for the project / reliability of the code base.
I have myself tested this to, and imposed this limit on a local mysql server, and ran a Vbulletin install with 10k members, 60k posts , and had no issues whatsoever, however a phpbb3 install fails VERY VERY quickly with this limit. I understand why this limit is placed by hosters (to stop rogue queries / inner / outer joins zapping shared mysql resources, and as 95% of phpbb installs will be on shared servers this really should be addressed.
Please could one of the phpbb dev team look into these joins in the acp !![/quote]
Please don't close this ticket because you could get this working by just increasing the max_join_size, the problem would still be there. A developer said that phpbb3 does a lot more in the ACP as the forum group my forum is just as Kevin_m1 described, if you at least could explain in public what phpbb does that requires 500,000 rows being queried and why vbulletin doesn't it would be nice to the community to know it.