Notifications
Clear all

[Closed] Performance

16 Posts
3 Users
0 Reactions
11 K Views
Posts: 33
 jost
Topic starter
(@jost)
Eminent Member
Joined: 7 years ago

I just gave wpForo a go with a 300K+ forum, imported from bbPress.

The import script went flawless.

Then I loaded tested the bbPress forum versus the wpForo forum.
I simulated 200 users for 1 minute.  Here are the results.

bbPress result attached

 

15 Replies
Posts: 33
 jost
Topic starter
(@jost)
Eminent Member
Joined: 7 years ago
Posts: 33
 jost
Topic starter
(@jost)
Eminent Member
Joined: 7 years ago

wpForo average response time was a little less than HALF of bbPress.

 

However, it still was nowhere close to non-wordpress based forum software so I ran a profile on a page where I was reading a topic.

wpForo executed over 360 SQL queries just for reading a topic.

Compare that to my old phpBB forum which only executes 16.

Although a nice improvement over bbPress, it just doesnt perform fast enough for our clients 🙁

I could run 30 phpBB forums on the same hardware versus wpForo.

Posts: 33
 jost
Topic starter
(@jost)
Eminent Member
Joined: 7 years ago

I also suspect that because wpForo does not use a unique INTEGER ID in its url's it is forced to run a SQL query against a CHAR column when searching for topics.  This is very slow when dealing with a forum that has 300K or 1 million+ posts.

I would suggest tweaking your software to add a unique postID to each URL for much faster queries.

And finally, please reduce the number of queries. Would love to use this software but I need it 10X faster than it is today.

 

Posts: 33
 jost
Topic starter
(@jost)
Eminent Member
Joined: 7 years ago

Checked on a query.

 

"SELECT *

FROM `wp_wpforo_topics`
WHERE `slug` ="   /etc

 

This is where you guys find the post via the slug. The query is surprisingly fast, so I stand corrected.  Doesnt seem to be a need for a unique INTEGER in the URL.

 

It seems the huge number of queries, all which are individually fast, when added together, cause a high load and a sluggish site.   > 1 second response time is too slow.

 

 

Page 1 / 4