Re: Choosing tables to convert to InnoDB
Hi Manual,
Couple of things: if you are not using transactions by default (though, you can set that in my.cnf). Using transaction can be sometimes faster for example for 10 INSERTS: needs to flush once, instead of 10 times after each statement.
Multiple tablespace. Well, depends on your harddrive. If you put all the tablespaces on the same disk, you will not gain much. If you span it over sperated disks, then you will gain some.
Maybe you can split up the big table in smaller tables and use MERGE engine?
If you are not going to use transactions, then why not stay with MyISAM? InnoDB also uses a bit more memory, might also be important.
Regards,
Geert
Subject
Views
Written By
Posted
3577
May 12, 2005 05:22AM
Re: Choosing tables to convert to InnoDB
2182
May 13, 2005 04:17AM
2266
May 16, 2005 03:19AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.