Topic: Twenty-four things you can do to make SMF go faster (Updated June 16th, 2010)

[roshaoar]

Thanks!

[vbgamer45]

If your mysql server is on the same machine change from connecting from localhost to 127.0.0.1 and get a big boost in some cases just saw this on one of my sites and it just had a massive increased in performance.
http://stackoverflow.com/questions/17815604/very-slow-1-second-connections

[青山 素子]

If your mysql server is on the same machine change from connecting from localhost to 127.0.0.1 and get a big boost in some cases just saw this on one of my sites and it just had a massive increased in performance.

That's really weird. Normally, localhost resolves internally and should add little to no overhead. If you have control over the server, make sure localhost is an entry in your hosts file.

[vbgamer45]

Yeah was shocked myself on my windows servers I updated it made a huge difference it for all my sites that that had databases on the same server.   The issue was php tries to look for ipv6 localhost first for mysql then ipv4. And mysql by default wasn't listening on ipv6.

[vbgamer45]

Another tip just discovered that the smf_sessions table last_update should have an index to add one run

Code: [Select]

alter table smf_sessions add index last_update (last_update);


[Arantor]

That's only if you're not doing the memcache thing

[vbgamer45]

That server does have memcache with level 3 smf caching I still saw that query hit though.

[Arantor]

Then turn off DB sessions and get PHP to use memcache for sessions.

[vbgamer45]

Will give that a shot and test.

[MobileCS]

8: Run the mark read for inactive users script periodically. The log_topics, log_boards, and log_mark_read tables are not the best designs, and for some unlucky folks end up dominating their database. Pruning them can help.

I think this should be rephrased. The "mark read for inactive users script" does not prune anything. In fact, it makes log_topics, log_boards and log_mark_read tables substantially larger.

What exactly is the benefit of running this script again?

[Arantor]

It prunes one set of tables and outs records in the other because if the way SMF works. It just so happens that for you it made it bigger, this is not universally true.

[albertlast]

Another tip just discovered that the smf_sessions table last_update should have an index to add one run

Code: [Select]

alter table smf_sessions add index last_update (last_update);


Don't do this kind of advice based on your wrong setup smf.
index slow down dml actions.

[MobileCS]

It prunes one set of tables and outs records in the other because if the way SMF works. It just so happens that for you it made it bigger, this is not universally true.

Ok, after going through the code more carefully, I can see what you're talking about.

In my opinion, this script should ignore users with 0 posts. I've modified my version to do just that. On my forum, I have lots of registered users that just want to access members only content.

This will clear up more than 750,000 entries in the smf_log_mark_read table alone.

[Arantor]

In my opinion, the script is fine for normal use, and your use case is atypical, such that changing the script generically will hurt more people than it would help.

[albertlast]

The hint to switch from localhost to 127.0.0.1 is only valid for Windows server,
On Linux your hurt yourself because mysql use on localhost socket connection and
On 127.0.0.1 tcp/ip.
Socket >tcp/ip