so you recommend then to change topic_markers to InnoDB?

He said that he did NOT recommend this. :)

 

He said that he did NOT recommend this. :)

are you sure?

cause I see this post which is topic_markers:
http://www.ipsbeyond.com/forums/index.php?...ost&p=76235

Where brandon says to.

then this post:
http://www.ipsbeyond.com/forums/index.php?...ost&p=76502

brandon says TO NOT do the POSTS table

 

MyISAM is the fastest engine in mysql for searching. Since the posts and topics tables are frequently searched, changing to innodb would kill your site most likely, if it were large. Forget the locked queries, searches will bring the server down.

I based my asnwer off of this. Sorry for not remembering something from a completely different page ;)

I do recommend changing topic_markers to InnoDB

What I've noticed on some larger sites is that you get queries that are trying to update the topic markers table (which happens nearly every time you load a topic) getting locked. This slows things down quite a bit (because then when you or other people try to view a topic, it won't finish loading till your query against the markers table actually runs).

The markers table isn't searched - it's just selected from based on a key, so I recommend changing it to innodb to prevent the locked queries against it.

Awesome, thanks for the info Brandon :)

Per bfarber's suggestion I did this today. I will feedback the performance change in a few days once I can get enough entries in the slow queries log to see if any more table locks occur. I had cascading table locks (one lock then another and another as load increased) all but freezing the forums from this. I wonder if by default this table should be InnoDB?

Is there any chance of IPB ever supporting postgres?

I hit paydirt recently by experimenting with key_cache_division_limit. I'm still figuring out works best but have been using numbers between 30 and 50.

Users have started topics on my "chit chat' type forum which they are pretty much using as blogs with some having 5000+ posts. I'm guessing that users checking in on each other in these every day has been making it hard for much of anything else to stay in the key cache for long and that's why switching to midpoint insertion has helped.

The dev.mysql page on it if anyone is curious
http://dev.mysql.com/doc/refman/4.1/en/mid...-insertion.html

 

Is there any chance of IPB ever supporting postgres?

I hit paydirt recently by experimenting with key_cache_division_limit. I'm still figuring out works best but have been using numbers between 30 and 50.

Users have started topics on my "chit chat' type forum which they are pretty much using as blogs with some having 5000+ posts. I'm guessing that users checking in on each other in these every day has been making it hard for much of anything else to stay in the key cache for long and that's why switching to midpoint insertion has helped.

The dev.mysql page on it if anyone is curious

http://dev.mysql.com/doc/refman/4.1/en/mid...-insertion.html

Very interesting... how much has this impacted (good or bad) performance?

I can't say on postgres driver - I had heard through the grapevine someone mentioned working on one after 2.2 final was released. Guess we'll see?

On televisionwithoutpity.com - there is one topic that is over 13,000 pages long (pages, not posts - meaning at 30 posts a page you're looking at around 390,000 posts in one topic).

http://forums.televisionwithoutpity.com/in...view=getnewpost