On Aug 17, Jesper Noehr <[EMAIL PROTECTED]> wrote: > What you might want to do is set "innodb_file_per_table"
Done and it partially solves the problem, but building the indexes is still way too slow. > > The real problem is running imdbpy2sql.py with a database set to > > use InnoDB: after all the data were processed, it takes forever > > (or a good approximation of forever ;-) to build indexes. > > It *will* take a long time, yes, which is why doing an ALTER TABLE > is easier. I just thought perhaps we should give people the choice > when they initially install it. It might be a poweruser feature > and they can figure it out themselves.. I'm still unsure about what can really be done in the imdbpy2sql.py script: so far the only thing I can think of is to document the possibility to convert the tables after they were populated as MyISAM. > 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? Thank you for the help! -- Davide Alberani <[EMAIL PROTECTED]> [PGP KeyID: 0x465BFD47] http://erlug.linux.it/~da/ ------------------------------------------------------------------------- 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
