According to the thread, a large topic with many posts would be slow to display the last page. Upon further inspection they found that such slow queries often join many tables and use the LIMIT clause in a single query, just like the query rellsh posted two years ago. They tried several alternatives before settling for rewriting the slow query into two smaller one, one that gets post IDs and one that joins those post IDs.
Just thought their approach might also help solve rellsh's problem. Have Vanilla 2 already adopted similiar solutions on that kind of database queries?
Comments
According to the thread, a large topic with many posts would be slow to display the last page. Upon further inspection they found that such slow queries often join many tables and use the LIMIT clause in a single query, just like the query rellsh posted two years ago. They tried several alternatives before settling for rewriting the slow query into two smaller one, one that gets post IDs and one that joins those post IDs.
A user reported that on a topic with 17K posts, the two-query approach reduced total time from about 0.5-0.6s to 0.02-0.03s (http://fluxbb.org/forums/viewtopic.php?pid=32255#p32255).
Just thought their approach might also help solve rellsh's problem. Have Vanilla 2 already adopted similiar solutions on that kind of database queries?