Welcome, Guest. Please login or register.

Author Topic: Changed from MyISAM to InnoDB  (Read 1744 times)

sjobergh

  • Newbie
  • *
  • Posts: 24
    • View Profile
Changed from MyISAM to InnoDB
« on: May 25, 2016, 01:02:26 AM »
and it seems to work good,  no table locks anymore and I think I gained about 30%-40% in speed/time when doing discovery

sjobergh

  • Newbie
  • *
  • Posts: 24
    • View Profile
Re: Changed from MyISAM to InnoDB
« Reply #1 on: May 25, 2016, 01:03:51 AM »
Only useful if you have parallel discovery sessions/tasks

dohco

  • Newbie
  • *
  • Posts: 27
    • View Profile
Re: Changed from MyISAM to InnoDB
« Reply #2 on: May 25, 2016, 12:59:37 PM »
Interesting!
Do you have a "manual" or any documentation on how you did the conversion?

Regards
/Conny

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2558
    • View Profile
    • NeDi
Re: Changed from MyISAM to InnoDB
« Reply #3 on: May 26, 2016, 10:30:17 AM »
Interesting indeed! I read about difference of the two, but never thought I'd affect it so much!
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

swepart

  • Newbie
  • *
  • Posts: 11
    • View Profile
Re: Changed from MyISAM to InnoDB
« Reply #4 on: June 01, 2016, 05:30:05 PM »
It was pretty easy, I just followed one of several instructions I found on the net
basically only one command per table

Before you alter the tables,  stop all jobs that connected to database

then:
ALTER TABLE tablename ENGINE=InnoDB;

When you are done with all tables you should edit "my.cnf" with InnoDB parameters that is adjusted for you hardware
You might have "fiddle" around with the different InnoDB parameters,  some of them made my installation unusable but when taking them out it works again

I ended up with just these two rows
innodb_thread_concurrency=8
innodb_buffer_pool_size=2G


then you have to restart mysql engine,