Mikel, ----- Original Message ----- From: "Mikel -" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, January 21, 2004 7:19 PM Subject: Re: Too slow recovering mysqldump files
> I'll set up those parameters in my.cnf and try again the recovery from the > dump file. I'll hope these changes make faster the recovery. Dr. Ullrich suggested that you should set innodb_flush_log_at_trx_commit=0 during the big import, or wrap the big import inside a transaction. Otherwise, the speed may be restricted to 1 row / disk rotation = 100 rows/second. > Thanks again Heikki, > > Mikel > > P.S. Do you recommend the innodb hot backup tool, does it do faster than the > other options, or is a combination of both? InnoDB Hot Backup takes a BINARY backups of your database. If you need to restore from a backup taken with InnoDB Hot Backup, you do not need to import table dumps. Thus restoration is much faster than if you use table dumps as a backup (table dump = LOGICAL backup). Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables Order MySQL technical support from https://order.mysql.com/ > >From: "Heikki Tuuri" <[EMAIL PROTECTED]> > >To: "Mikel -" <[EMAIL PROTECTED]> > >CC: <[EMAIL PROTECTED]> > >Subject: Re: Too slow recovering mysqldump files > >Date: Wed, 21 Jan 2004 05:10:27 +0200 > > > >Mikel, > > > >it is apparently disk-bound. > > > >I recommend setting innodb_buffer_pool_size as high as 1.4 GB during such > >big import. Adjust innodb_log_file_size accordingly, and make key_buffer > >smaller during the big import. > > > >Help is coming: Marko Mäkelä is writing a compressed InnoDB table format, > >which can squeeze a typical table to 1 / 4 the size of a normal InnoDB > >table. I believe the compressed format will be available in October 2004. > > > >Best regards, > > > >Heikki Tuuri > >Innobase Oy > >http://www.innodb.com > >Foreign keys, transactions, and row level locking for MySQL > >InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM > >tables > > > >Order MySQL technical support from https://order.mysql.com/ > > > > > >----- Original Message ----- > >From: "Mikel -" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Cc: <[EMAIL PROTECTED]> > >Sent: Wednesday, January 21, 2004 12:32 AM > >Subject: Re: Too slow recovering mysqldump files > > > > > > > Here we are my options: > > > > > > set-variable = innodb_log_file_size=150M > > > set-variable = innodb_log_buffer_size=8M > > > > > > I follow the example that came here: > > > "http://www.mysql.com/doc/en/InnoDB_start.html"; > > > > > > Greetings and best regards > > > > > > Mikel > > > > > > > > > >From: "Heikki Tuuri" <[EMAIL PROTECTED]> > > > >To: <[EMAIL PROTECTED]> > > > >Subject: Re: Too slow recovering mysqldump files > > > >Date: Mon, 19 Jan 2004 22:44:50 +0200 > > > > > > > >Mikel, > > > > > > > >have you set the size of the InnoDB log files as recommended in the > >manual? > > > > > > > >Best regards, > > > > > > > >Heikki Tuuri > > > >Innobase Oy > > > >http://www.innodb.com > > > >Foreign keys, transactions, and row level locking for MySQL > > > >InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up > >MyISAM > > > >tables > > > > > > > >Order MySQL technical support from https://order.mysql.com/ > > > > > > > >----- Original Message ----- > > > >From: ""Mikel -"" <[EMAIL PROTECTED]> > > > >Newsgroups: mailing.database.myodbc > > > >Sent: Monday, January 19, 2004 7:25 PM > > > >Subject: Too slow recovering mysqldump files > > > > > > > > > > > > > Hi list, does anyone know a faster way to recover a mysqldump file > > > >cause > > > > > When I recovered one dump file it took 26 hours ! to finish, I think > > > >it's > > > > > too slow. > > > > > Thnx in advanced, greetings > > > > > > > > > > MySQL server 3.23.58 > > > > > RedHat 7.3 > > > > > 4GB RAM > > > > > 2 scsi disk via fiber channel (333GB each) > > > > > 2 processor Xeon 1.6GHZ > > > > > > > > > > dump file size: 2.5 GB > > > > > ibdata: 11GB > > > > > innodb tables > > > > > key_buffer=850M > > > > > innodb_buffer_pool_size=850M > > > > > table_cache=1500 > > > > > > > > > > _________________________________________________________________ > > > > > MSN. Más Útil Cada Día http://www.msn.es/intmap/ > > > > > > > > > > > > > > > -- > > > > > MySQL General Mailing List > > > > > For list archives: http://lists.mysql.com/mysql > > > > > To unsubscribe: > > > >http://lists.mysql.com/[EMAIL PROTECTED] > > > > > > > > > > > > > > > > >-- > > > >MySQL General Mailing List > > > >For list archives: http://lists.mysql.com/mysql > > > >To unsubscribe: > >http://lists.mysql.com/[EMAIL PROTECTED] > > > > > > > > > > _________________________________________________________________ > > > MSN. Más Útil Cada Día http://www.msn.es/intmap/ > > > > > > > _________________________________________________________________ > MSN Fotos: la forma más fácil de compartir e imprimir fotos. > http://photos.msn.es/support/worldwide.aspx > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
