For example, categorylinks.sql
http://download.wikimedia.org/enwiki/latest/enwiki-latest-categorylinks.sql....
When extracted, around 1.3 GB, I have started the importing on a P3 1G with 256RAM, the job is running more than 1 day now.
Sure I have lock the table, disable indexing, disable unique key check ect...and followed the recommended InnoDB settings as in MySQL Manual.
May I should try MyISAM later to compare.
But anyone has experience in slow importing?
Howard
When I tried to import categorylinks.sql, MySQL crashed and the table was pretty badly corrupted. I couldn't prevent this - if anyone knows how, please share :) - so I loaded the whole lot into PostgreSQL, which ran without any problems. Categorylinks.sql shouldn't take too long (depending on your computer of course).
Geoff
On 8/06/2008, at 4:53 PM, howard chen wrote:
For example, categorylinks.sql
http://download.wikimedia.org/enwiki/latest/enwiki-latest-categorylinks.sql....
When extracted, around 1.3 GB, I have started the importing on a P3 1G with 256RAM, the job is running more than 1 day now.
Sure I have lock the table, disable indexing, disable unique key check ect...and followed the recommended InnoDB settings as in MySQL Manual.
May I should try MyISAM later to compare.
But anyone has experience in slow importing?
Howard
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi
On Wed, Jun 11, 2008 at 8:56 AM, Geoff Munn geoff@zimoobo.com wrote:
When I tried to import categorylinks.sql, MySQL crashed and the table was pretty badly corrupted. I couldn't prevent this - if anyone knows how, please share :) - so I loaded the whole lot into PostgreSQL, which ran without any problems. Categorylinks.sql shouldn't take too long (depending on your computer of course).
Geoff
I have tried using MyISAM, now import take less than one hour, compare with using InnoDB for more than One day.
Howard
howard chen wrote:
Hi
On Wed, Jun 11, 2008 at 8:56 AM, Geoff Munn geoff@zimoobo.com wrote:
When I tried to import categorylinks.sql, MySQL crashed and the table was pretty badly corrupted. I couldn't prevent this - if anyone knows how, please share :) - so I loaded the whole lot into PostgreSQL, which ran without any problems. Categorylinks.sql shouldn't take too long (depending on your computer of course).
Geoff
I have tried using MyISAM, now import take less than one hour, compare with using InnoDB for more than One day.
Maybe you need to increase your InnoDB buffer pool size.
-- Tim Starling
On Thu, Jun 12, 2008 at 10:12 PM, Tim Starling tstarling@wikimedia.org wrote:
Maybe you need to increase your InnoDB buffer pool size.
You should probably read something like this on basic InnoDB configuration:
http://www.mysqlperformanceblog.com/2007/11/01/innodb-performance-optimizati...
If you keep the default values, like 8M buffer pool, you're not going to get a functioning database under any reasonable load. Using MyISAM with MediaWiki may cause problems and is not recommended, although it will probably more or less work.
wikitech-l@lists.wikimedia.org