Support Forum
It is a private forum, but I'd be happy to send over login details if you'd be willing to take a quick look.
We do have a lot of WP plugins, but it's a bit harder to dial in the conflict since the issue is sporadic. I will check to see which plugins have not been updated in awhile.
Thanks.
Mostly it does not come across as being that slow to me although I did see the odd and sudden slowdown where it looked like it was waiting for a server slot to become available. I don't know what sort of contention for the server you experience of course nor how well your hosting copes with it.
I did see the same odd (and it really was occasional) sudden wait on all areas pf the website not just the forum page. Considering that the forum loads dynamic data that is also compiled specifically for the user loading the page and the rest of the site tends to be static data then it is clear that the forum page would take a little longer to display but I didn't really notice much difference. Yours is also pretty light on the javascript files being loaded which came as a surprise after you saying you used lots of WP plugins.
I do not know how your mySQL is set up and I have no experience of optimising mySQL but if you have a high contention rate and lots of concurrent users on the site much of the time then you might want to consider switching to InnoDB tables if you are not using them now. Most hosts seem to always set up and default to the MyISAM engine which is fine most of the time, But when things get busy - especially if there is a lot of db 'writing' activity as one can experience with a forum, then InnoDB tables are better placed to take the strain. When myISAM needs to lock data for changes it locks the whole table whereas InnoDB only locks the table rows needed. But this would be a minor change on the whole.
The bottom line for me personally was that if this were my site I would be relatively happy with the performance bit would want to try and solve that occasional longish wait that seems to randomly happen.
YELLOW
SWORDFISH
|
Hi guys. I'm back with an update and a quick question.
Per your suggestion, we had our hosting guys make the move from myISAM to InnoDB for our db tables today. Some of our tables were using myISAM and some were using InnoDB. Hosting guys said the mySQL default is InnoDB, but some plugins change their tables to myISAM!?
They converted all myISAM tables to InnoDB except for two.
wp_sfposts
wp_sftopics
Because of this error: "ERROR 1214 (HY000) at line 1: The used table type doesn't support FULLTEXT indexes ERROR 1214 (HY000) at line 1: The used table type doesn't support FULLTEXT indexes"
Does that sound right to you guys? Do you know if those tables should be able to use InnoDB?
Thanks again for all the help.
Pete
Tell your guys to remove those 2 indices and resubmit the tables to innoDB. This is what out InnoDB conversion plugin does. And that will be fine as long as your SP is an up to date version, say, newer than a year ago which is about when we made the necessary changes to abandon those indices.
YELLOW
SWORDFISH
|
Yellow Swordfish said
This is what out InnoDB conversion plugin does
What and where is this InnoDB conversion plugin you speak of?
I have considered converting our db tables from MyISAM to innoDB for quite some time, but have been daunted by the task after reading up on it.
I see no such download in the SP Plugins.
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Oddly - we wrote the small plugin to help a user - decided to offer it and then promptly forgot about it! This was about a year back. It IS going to make an appearance in a few weeks when we rework the website here.
Not swapping the database engine is really not hard. It can be done manually in phpMyAdmin at table level. It was just the two tables referred to that had indexing unsupported by innoDB. I have attached a copy of the plugin you can try. Running it multiple times has no ill-effect although it should just do the job on the first pass. It is a WP plugin and adds an item to the forum menu. When done it should just be deactivated and removed. The plugin is a bit utilitarian by the way - nothing fancy!
Make a backup first? Always 🙂
YELLOW
SWORDFISH
|
Yellow Swordfish said
Not swapping the database engine is really not hard....I have attached a copy of the plugin...
Thanks! I'll start a new topic if I have questions...
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
1 Guest(s)