- Things To Know
- Rotation (Thumbs CMS) (V 2.X)
- Admin Area
- Traffic Rules
- New Style Rotation
- Custom Galleries
- Tube Sites
- Old Style Rotation
- New Trade - Add Trade
If you use only trade part of the script - it's not really important. Trade part doesn't really load mysql. This article is for those who use built-in rotation, especially with big databases.
Mysql, as almost any other DB, stores data on disk. Disk operations are slow (compared to in-memory operations) and that's is why very important to use indexes. There are basically 2 storage engines (mysql has more then 11 actually but only 2 are important in our case) - MyISAM and InnoDB.
MyISAM can load only indexes in memory while innodb can load both indexes and data itself. Thus we have two points to consider: if we don't have enough memory - we'd batter use myisam, but if we do have enough memory to load both indexes and data - we can get a great improvement in terns of performance. But if we don't have enough memory and try to use Innodb - it will be slower then myisam. Conclusion: InnoDB is batter if you have enough memory. If you don't - use MyIsam.
As we don't know what kind of server you gonna use - default engine is MyISAM
Here's what you need to move to InnoDB:
For MyISAM and InnoDB both:
While you can convert all tables into Innodb , I would not recommend it as it's waste of memory that could be use by system to cache files, thumbs for example. It really makes sense to convert rot_* tables and that's it.