Also depends on your data access pattern as well. If you can take advantage of clustering my primary key for your selects, then InnoDB could do it for you. My suggestion would be to write some queries based on projected workload, build 2 tables with lots and lots of data, and do some isolated testing. For work, I do a lot of query profiling using maatkit. Be sure to clear out as much of the caching as possible including the OS cache.
On Mon, Apr 5, 2010 at 7:25 AM, Jan Steinman <j...@bytesmiths.com> wrote: >> From: Gavin Towey <gto...@ffn.com> >> >> InnoDB should be your default for all tables, unless you have specific >> requirements that need myisam. One specific example of an appropriate task >> for myisam is where you need very high insert throughput, and you're not >> doing any updates/deletes concurrently. > > A couple other things: InnoDB does relations better, MyISAM does search of > text fields. > > > ---------------- > If we can control fuel we can control the masses; if we can control food we > can control individuals. -- Henry Kissinger > :::: Jan Steinman, EcoReality Co-op :::: > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=kykim...@gmail.com > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
