Max post per thread

[minskog]

SMF Version: SMF 1.1 RC2
What is the recomended max number of pages in a thread in smf 1.1-rc2?

I have threads over 200 pages ....

[Ben_S]

The number of pages shouldn't really cause an issue.

[minskog]

The number of pages shouldn't really cause an issue.

thank you, (I just asked this) to make sure I'm covering the basics
I updated to 1.1-rc2 and still the forum keeps crashing.

[Ben_S]

My longest topic is 312 pages long @ 40 posts per page.

[minskog]

616 pages @ 15 per page-> http://www.masquechicos.com/foro/index.php/topic,37106.0.html
401 pages @ 15 per page -> http://www.masquechicos.com/foro/index.php/topic,41620.0.html
374 pages @ 15 per page -> http://www.masquechicos.com/foro/index.php/topic,38539.0.html

The biggest ones, then you have more post than I, other thing discarted ... im lost

[Ben_S]

Do you have the basic html option enable, if so try turning it off temporarily.

[minskog]

I only permit bbcode. I have bbdd biggest than this forum and i don't have any problems. I dont known what happened with this site.

[Ben_S]

Have you checked everything listed in this topic > http://www.simplemachines.org/community/index.php?topic=49999.0

[minskog]

Yes, but now i dont have innodb tables beacuse i dont known what tables are needed in smf 1.1-rc2

[Ben_S]

The same as whats in that thread pretty much plus all the log_search ones, although that wouldn't cause the slowdown,

[minskog]

thanks for the info and for your patience 

[minskog]

I detected that all slow querys are the same:

CREATE TEMPORARY TABLE smf_topics_posted_in (
                                PRIMARY KEY (ID_TOPIC)
                        )
                        SELECT ID_TOPIC, ID_BOARD
                        FROM smf_messages
                        WHERE ID_MEMBER = 450
                        GROUP BY ID_TOPIC;

[Ben_S]

Thats the horrible show posts of a user feature, I'm hoping those querys will be rewritten by the time 1.1 goes final, as it currently is with a large number of posts it's a server killer.

[minskog]

Thats the horrible show posts of a user feature, I'm hoping those querys will be rewritten by the time 1.1 goes final, as it currently is with a large number of posts it's a server killer.

thanks. I've just have migrated to innodb. As a result, right now the load has gone down a little. I continue looking for the cause of the load

In this forum we'll never walk alone ...

[Ben_S]

You may want to disable the show users posts feature when the load is high, on mine I disable it when the load is above 2, see http://www.simplemachines.org/community/index.php?topic=76249.0

[minskog]

You may want to disable the show users posts feature when the load is high, on mine I disable it when the load is above 2, see http://www.simplemachines.org/community/index.php?topic=76249.0

Thanks, but now are burnig the server again:Load average: 14.32 8.03 6.18

With this feature active:

Lock wait timeout exceeded; try restarting transaction
File: /usr/var/www/virtual/web1/web/foro/Sources/Display.php
Línea: 140


My innodb conf:

innodb_buffer_pool_size         = 16M
innodb_additional_mem_pool_size = 2M
innodb_data_file_path           = ibdata1:100M;ibdata2:100M:autoextend
innodb_log_file_size            = 5M
innodb_log_buffer_size          = 8M
innodb_flush_log_at_trx_commit  = 1
innodb_lock_wait_timeout        = 50


Then, this need more than 50 seconds to execute transactions.

[Ben_S]

Whats the entire contents of your my.cnf?

[minskog]

Whats the entire contents of your my.cnf?

Code Select Expand


[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock


[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/english
skip-external-locking
old_passwords   = 1
bind-address            = 127.0.0.1
max_allowed_packet      = 16M
thread_stack            = 128K
max_connections=500
thread_cache_size=50
key_buffer=40M
table_cache=384
sort_buffer_size=768K
read_buffer_size=512K
read_rnd_buffer_size=512K
thread_concurrency=2
query_cache_limit       = 1048576
query_cache_size        = 16777216
query_cache_type        = 1
log-slow-queries        = /var/log/mysql/mysql-slow.log
log-bin                 = /var/log/mysql/mysql-bin.log
max_binlog_size         = 104857600
skip-bdb
innodb_buffer_pool_size         = 16M
innodb_additional_mem_pool_size = 2M
innodb_data_file_path           = ibdata1:100M;ibdata2:100M:autoextend
innodb_log_file_size            = 5M
innodb_log_buffer_size          = 8M
innodb_flush_log_at_trx_commit  = 1
innodb_lock_wait_timeout        = 50

[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]

[isamchk]
key_buffer              = 16M


[Ben_S]

Are you using MySQL replication, I assume not so comment out these lines

log-bin                 = /var/log/mysql/mysql-bin.log
max_binlog_size         = 104857600

Increase table_cache to 900

Reduce sort_buffer_size to 512K, this is a per connection setting so that should save some ram and you only have 500MB.

[minskog]

i change this parameters and now: 119 (0 sleeping, 3 running, 116 locked)