On 8/17/07, Davide Alberani <[EMAIL PROTECTED]> wrote: > On Aug 17, Jesper Noehr <[EMAIL PROTECTED]> wrote: [...] > > But then again, importing to MyISAM takes a good while too. How > > long did you let it run for? > > Using MyISAM it takes about 2 hours on my PC (slow and a bit busy), of > which about 20/25 minutes spent building indexes. > Using InnoDB it takes about 2 hours to put the data in the db, > and then after another 1 hour and an half it was still building the index > for the cast_info table (only aka_name and aka_title were completed). > I'm surprised by these numbers: building an index shouldn't take > _so_ long (after we're not working on a database so big). > > Ideas?
Hi Davide, I searched around a bit, and it seems that it is recommended that the indexes are added before inserting data, although I'm not exactly sure why. I found this old thread, though: <URL: http://lists.mysql.com/mysql/139208 > "currently, CREATE INDEX, DROP INDEX, and most ALTER TABLE's rebuild the whole table in MySQL. It is in the TODO to make this behavior more sensible. DROP INDEX would be essentially instantaneous, and CREATE INDEX would only build the new index." Of course, this statement is pretty old (from 2003), so I don't know if it still works like that. [...] -- Vetle Roeim ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Imdbpy-devel mailing list Imdbpy-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/imdbpy-devel
