Why IP.Board not use INNODB? INNODB "is safer" than MyISAM

You can change your table types to innodb if you wish.

That's not true because when I tried change table ipb_posts

alter table ipm_posts engine=innodb;

I saw:

The used table type doesn't support FULLTEXT indexes

Only some tables I can change
for example: members, forums

INNODB is not "safer" than MYISAM. It is "better" for inserting data because it implements row-level locking, but technically MYISAM is "safer" because it uses table-level locking. MYISAM is also faster when reading. MYISAM is good for smaller communities, but for larger communities you usually want to use something like INNODB because the new post rate is much higher. If you want to convert a MYISAM table with FULLTEXT to INNODB you have to drop the FULLTEXT indexes and turn off FULLTEXT searching (IPB setting, right?). A good replacement for FULLTEXT is Spynx.

You have old news :D
InnoDB "is safer" because have automatic crash recovery. In case shutdown You needn't check/repair database (MyISAM may require).
Look here:
http://en.wikipedia.org/wiki/MyISAM
http://en.wikipedia.org/wiki/InnoDB

You have old news :D

InnoDB "is safer" because have automatic crash recovery. In case shutdown You needn't check/repair database (MyISAM may require).

Look here:

[url="http://en.wikipedia.org/wiki/MyISAM"]http://en.wikipedia.org/wiki/MyISAM[/url]

[url="http://en.wikipedia.org/wiki/InnoDB"]http://en.wikipedia.org/wiki/InnoDB[/url]

Really? What version of MySQL do you need to for the "improved innodb"? Most servers are still using MySQL 5.0, and 5.1 if you're lucky.

INNODB is not "safer" than MYISAM. It is "better" for inserting data because it implements row-level locking, but technically MYISAM is "safer" because it uses table-level locking. MYISAM is also faster when reading. MYISAM is good for smaller communities, but for larger communities you usually want to use something like INNODB because the new post rate is much higher. If you want to convert a MYISAM table with FULLTEXT to INNODB you have to drop the FULLTEXT indexes and turn off FULLTEXT searching (IPB setting, right?). A good replacement for FULLTEXT is Spynx.

INNODB is a lot slower at inserting rows into a DB though compared to MYISAM. Although this won't be a big issue on a few queries on lots its a page killer.

INNODB also isn't crash proof..


And yes you CAN convert to INNODB , you just need to disable full text searching, but the self proclaimed DBA you seem to be should know that...

In our experience, using InnoDB has caused problems. If it crashes, there is no repair at all - you must restore from a backup. It's much slower with a lot of activity, as well, despite supporting row-level locking vs table-level locking. This is just anecdotal experience, however. We understand others have had different experiences (some users have had MUCH different experiences in fact), and there is absolutely nothing stopping you from using InnoDB if you so wish.

If you wish to do so, you cannot use MySQL fulltext searching (since InnoDB doesn't support fulltext indexes), so you should consider using Sphinx for search.

Either way, we do not intend to ship with InnoDB set as the default on installation. You're free to configure *your* community to your liking as you deem fit.

On my friends website, he was having 300 QPS and MyISAM table where having issues.

He converted few tables to InnoDB and slowness of website was fixed. I guess it's all depend on load, set up and needs.

In our experience, using InnoDB has caused problems. If it crashes, there is no repair at all - you must restore from a backup. It's much slower with a lot of activity, as well, despite supporting row-level locking vs table-level locking. This is just anecdotal experience, however. We understand others have had different experiences (some users have had MUCH different experiences in fact), and there is absolutely nothing stopping you from using InnoDB if you so wish.

If you wish to do so, you cannot use MySQL fulltext searching (since InnoDB doesn't support fulltext indexes), so you should consider using Sphinx for search.

Either way, we do not intend to ship with InnoDB set as the default on installation. You're free to configure *your* community to your liking as you deem fit.

Yea i recently was working with INNODB and doing inserts were taking 20x longer than with MyISAM. Using iNNODB was an oversight though and once fixed everything worked fantastic again.

Yea i recently was working with INNODB and doing inserts were taking 20x longer than with MyISAM. Using iNNODB was an oversight though and once fixed everything worked fantastic again.

Different database engines serve different tasks. We ran a MySQL database that grew to 5TB in my old job, and MyISAM tables just didn't stand a chance, InnoDB was the only database engine that could handle it.

Everyone's choice of what engine to use should be dependent on their individual circumstances, InnoDB will work amazingly for some people, whilst others will have trouble, there are too many factors to make a blanket "use this" statement.

What about other engines other than MySQL? How do they compare? (Free, or not; Not strictly IPB)

What about other engines other than MySQL? How do they compare? (Free, or not; Not strictly IPB)

Percona + XtraDB (InnoDB+) is awesome!

could You tell something more why do You think so?

could You tell something more why do You think so?

The performance of XtraDB (via Percona MySQL Server) compared to MySQL + InnoDB [standard] is outstanding. vBulletin posted metrics here: http://www.vbulletin.com/forum/entry.php/2428-vB4Mance-Part-3-Database-performance-vB-benchmark-with-Percona-XtraDB-5.5-5.1, but in the benchmarks I've done, I yielded even better results.