Hello.
If you send your configuration file there might be much more suggestions. In my opinion SET AUTOCOMMIT=0 before update should improve performance (don't forget to COMMIT after transaction). If you're sure in your data you can SET FOREING_KEY_CHECK=0 and SET UNIQUE_CHECKS=0. See: http://dev.mysql.com/doc/mysql/en/innodb-tuning.html javabuddy <[EMAIL PROTECTED]> wrote: > On an InnoDB table for 70k records the update action is taking so much > time.(More than 30minutes). We got the innodb_buffer_pool_size as 4gigs. IS > there anything more to add up to get the processes kick its speed. > > - javabuddy. > > > > ---------------------------------------------------------------------------------------------------- > People are conversing... without posting their email or filling up their mail > box. ~~1123523333645~~ > roomity.com http://roomity.com/launch.jsp No sign up to read or search this > Rich Internet App > ---------------------------------------------------------------------------------------------------- > > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
