Results 1 to 3 of 3

Thread: MyISAM to read records and InnoDB to write?

  1. #1
    Join Date
    Nov 2008

    MyISAM to read records and InnoDB to write?


    I read a while ago that if a database gets heavy traffic, then it's best to have MyISAM to read the records (fast) and have another database engine like InnoDB to write the records to the database (reliability). I'm looking for more information on this, but I can't find any.

    Can anyone tell me how this works and if there are any good tutorials on it?


  2. #2
    Join Date
    Aug 2005
    The Garden State
    the reason you can't find information about this topic is because it's not true. PHP developers have a few misunderstandings about what a transactional database engine is and isn't. myisam is considered good at querying because it's select speed is faster than its insert/update/delete, not because its select speed is faster than InnoDB. this is also why mysql is working on creating Falcon (not to mention that formerly, innodb was bought by their former competitor, now owner, oracle).

    here, take a look this from the performance blog, it was released when falcon was first released

    Acceptable Use | SQL Forum FAQ | celery is tasteless | twitter

    celery is tasteless - currently needing some UI time

  3. #3
    Join Date
    Mar 2005
    Sydney, Australia
    Also each table in your database can only be of one type. The best that you could do if it were true that myisam were better for reading and inodb for writing would be to make those tables that contain mostly static data that is rarely updated myisam and those tables that are constantly updated inodb.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
HTML5 Development Center