Choosing tables to convert to InnoDB
Hello,
I'm using only MyISAM tables right now, but i'm going to convert some of them to InnoDB because of high concurrency.
I have small tables (few MB and few KBs) and big tables (few GB) with lots of concurrent access.
At first, i decided to convert all tables with high concurrency, but the overload that innodb produces is more than i expected, so i'm trying to guess if this overload is mainly produced by the small tables or the big ones.
I'm having trouble doing my own benchmarks to decide wich tables to convert, so i would appreciate help. Does anyone know if the innodb overload has to be with the size of the tables?.
By the way, i don´t need transactions, so it would be great if it can be desactivated this funcionality in innodb because of the overload it produces. This is not possible, isn´t it?.
Finally, once i decide the tables to convert, can i have better performance using multiple tablespaces?. All documentation about this only talks about winning flexibility to spare data through diferent partitions or disks, and flexibility to make backups and restores, but doesn´t talk about performance.
Thank you in advance,
Manuel Cameselle.
Subject
Views
Written By
Posted
Choosing tables to convert to InnoDB
3587
May 12, 2005 05:22AM
2191
May 13, 2005 04:17AM
2269
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.