Comments on: What to do with MySQL Full Text Search while migrating to Innodb ? http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/ Percona's MySQL & InnoDB performance and scalability blog Sat, 11 Feb 2012 16:45:54 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Baron Schwartz http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-711240 Baron Schwartz Sun, 17 Jan 2010 22:56:57 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-711240 Unless I'm missing your point, that would solve absolutely nothing. Unless I’m missing your point, that would solve absolutely nothing.

]]> By: heradas http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-711150 heradas Sun, 17 Jan 2010 19:00:07 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-711150 how about just using mysql cluster? that should the prblem how about just using mysql cluster? that should the prblem

]]> By: peter http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-652545 peter Mon, 14 Sep 2009 15:18:15 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-652545 Chritopher, Yes. Everything has a cost. I would see it same as running memcache or other caching system with MySQL - you increase complexity you get performance. About Migrations - Sphinx is a separate server and can be moved separately from MySQL. Also because it pulls data from MySQL you can often move MySQL, when get the new sphinx installation running off that MySQL and when stop using old one. Chritopher,

Yes. Everything has a cost. I would see it same as running memcache or other caching system with MySQL – you increase complexity you get performance.

About Migrations – Sphinx is a separate server and can be moved separately from MySQL.
Also because it pulls data from MySQL you can often move MySQL, when get the new sphinx installation running off that MySQL and when stop using old one.

]]> By: peter http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-652540 peter Mon, 14 Sep 2009 15:13:54 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-652540 Jan, Do not forget MyISAM is pretty much always used for on disk temporary tables if you have Innodb so you never get off balancing problem completely. Also you need to balance memory between innodb buffer pool and OS cache which is needed for some things, query cache etc. Also setting it 50-50 is not a good method. The size and usage is what should drive the value. If there is single full text search table remains I would like to keep key_buffer same as .MYI takes (or expected to take) for the table. Jan,

Do not forget MyISAM is pretty much always used for on disk temporary tables if you have Innodb so you never get off balancing problem completely.

Also you need to balance memory between innodb buffer pool and OS cache which is needed for some things, query cache etc.

Also setting it 50-50 is not a good method. The size and usage is what should drive the value. If there is single full text search table remains I would like to keep key_buffer same as .MYI takes (or expected to take) for the table.

]]> By: Christopher Grello http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-652536 Christopher Grello Mon, 14 Sep 2009 15:05:39 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-652536 Since you're adding another item to the database environment you increase the complexity for day-to-day things, but also migrations. The benefits gained are certainly nice, but I'm curious if anyone has any good practice recommendations for migration Sphinx from one box to another when you need to move MySQL. Since you’re adding another item to the database environment you increase the complexity for day-to-day things, but also migrations. The benefits gained are certainly nice, but I’m curious if anyone has any good practice recommendations for migration Sphinx from one box to another when you need to move MySQL.

]]> By: Jan http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-652449 Jan Mon, 14 Sep 2009 12:08:15 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-652449 Peter, I assume your suggestion would be to e.g. give each database engine half the ram. Of course, that would work perfectly, but you are wasting precious memory. Having InnoDB and MyISAM "share" memory does not work very well. So yes, you can do it, but I think other methods are better. Peter, I assume your suggestion would be to e.g. give each database engine half the ram. Of course, that would work perfectly, but you are wasting precious memory. Having InnoDB and MyISAM “share” memory does not work very well.

So yes, you can do it, but I think other methods are better.

]]> By: peter http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-651710 peter Fri, 11 Sep 2009 16:19:16 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-651710 Jan, Mixing MyISAM and Innodb on the same server add balancing challenge but I think it is far from "not a good idea". You just need to consider your table sizes and usage pattern to balance between Innodb Buffer Pool size, Key Cache and OS Cache. Jan,

Mixing MyISAM and Innodb on the same server add balancing challenge but I think it is far from “not a good idea”. You just need to consider your table sizes and usage pattern to balance between Innodb Buffer Pool size, Key Cache and OS Cache.

]]> By: peter http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-651708 peter Fri, 11 Sep 2009 16:17:12 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-651708 Imran, Indeed if you create Shadow MyISAM table you would rarely keep it same as original table. You probably will not need a lot of indexes as well as many columns. Imran,

Indeed if you create Shadow MyISAM table you would rarely keep it same as original table. You probably will not need a lot of indexes as well as many columns.

]]> By: Jan http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-651631 Jan Fri, 11 Sep 2009 08:55:38 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-651631 Mixing InnoDB and MyISAM on a single server is not a good idea, due to memory allocation issues. So the only realistic option is a MyISAM slave. Or go Lucene/Solr. Mixing InnoDB and MyISAM on a single server is not a good idea, due to memory allocation issues. So the only realistic option is a MyISAM slave. Or go Lucene/Solr.

]]> By: imran http://www.mysqlperformanceblog.com/2009/09/10/what-to-do-with-mysql-full-text-search-while-migrating-to-innodb/comment-page-1/#comment-651612 imran Fri, 11 Sep 2009 07:57:40 +0000 http://www.mysqlperformanceblog.com/?p=1093#comment-651612 To add to the above though, I still prefer to use Sphinx for any InnoDB table warranting FT indexing. To add to the above though, I still prefer to use Sphinx for any InnoDB table warranting FT indexing.

]]>