I am running into a problem that I think should be addressed, but not sure exactly what or who...
My server isn't the best but is not a bad box either. I have a 16G ram 2X2.33Ghz box dedicated to the site. But when I have 100+ people online which is no uncommon for me the site starts to crawl... We have noticed that it is due to the 'datelastnav' field in the profile table. It does not allow for read and write, much less multiple connections at the same time. So the site begins to line up things to update this field, which slows everything down because if it is waiting to write to the field, it cant read it to display a profile for someone else either.
This field needs to be broken off to a separate table that is innodb capable. The software itself is fast, and can handle a ton of profiles, but it seems when you get a bunch of people online at the same time doing things it has a bit of a acheales heel.
Any ideas?
|
Hello we check it thank you PS: If possible do not write me personally, please try to ask on the forum first |
You can increase update time for DateLastNav to decrease database load for now.
Also is your database type InnoDB ? If not I suggest to switch to InnoDB this database engine has row level locking in comparison to MyISAM where whole table is locked.
For long term we will try to move to sessions, so only sessions table will be updated and DateLastNav field will not be needed at all.
Rules → http://www.boonex.com/terms |
what do you mean "increase update time for DateLastNav" Is this a setting in the admin panel or somewhere else?
Thank you for the quick response.
|
Wow, would like to know more about this also...
We have the same problem, site stalling when it reaches a certain number of online members (80 or so). This problem is increased by the number of concurrent connections each IP opens on our server (which is a very good one), connections are open with queries to the database and not closed, which hogs the servers resources and makes it unresponsive.
Now, we suspect this is exactly caused by profiles and photos browsing, so would love to have a way to end this problem.
Regards,
Sleepless |
what do you mean "increase update time for DateLastNav" Is this a setting in the admin panel or somewhere else?
Thank you for the quick response.
To test the job done with a table profiles using innoDB. Let us know the results of testing
PS: If possible do not write me personally, please try to ask on the forum first |
It appears that the profile table has fulltext indexing which is not supported by InnoDB. So we could not change it to that, doing so breaks the search on the site. |
It appears that the profile table has fulltext indexing which is not supported by InnoDB. So we could not change it to that, doing so breaks the search on the site.
You can use LIKE operator for searching (also this is default option).
This option can be changed here:
admin panel -> settings -> advanced settings -> variables -> Use operator LIKE for search (recommended for small content):
Rules → http://www.boonex.com/terms |
I do not have a small site, what will this affect over all? |
what do you mean "increase update time for DateLastNav" Is this a setting in the admin panel or somewhere else?
Thank you for the quick response.
It can be changed in inc/classes/BxDolMemberMenu.php file:
var $iBubblesUpdateTime = 30000; // in milliseconds;
But make sure that "Time period in minutes within which a member is considered to be online" is more than this setting:
"Time period in minutes within which a member is considered to be online" > iBubblesUpdateTime / 1000 / 60
Rules → http://www.boonex.com/terms |
