Carlos, ----- Original Message ----- From: ""Carlos Proal"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Friday, December 12, 2003 4:09 AM Subject: Innodb multiple tablespaces benchmark
> > > Hi all, specially to Heikki. > > Its really amazing that multiple tablespaces are available before 2004, > congratulations to Innodb Oy Inc. > > Right now im migrating from 4.1.0 to 4.1.1 but im figuring out if there is a > downgrade in performance in order to use multiple tablespaces, obviously it > must be one because handling several files adds an overhead but it something > to worry about ? a customer has been running benchmarks where he compared multiple tablespaces (each table in its own .ibd file) to the traditional single big ibdata file. He said the performance was about the same. > I thougt that these tablespaces would be for each database and not for each > table, this is possible ?, factible ?, useful ?, its scheduled ?. It is not possible in 4.1.1. I will look at customer feedback and add a more flexible tablespace concept if there is great demand. Most of the hard work was already done in 4.1.1. > Thanx a lot and again some claps for innodb :) Thank you :). > Carlos Oops! Now I realize I have forgotten to document the following my.cnf option in the manual: {"innodb_open_files", OPT_INNODB_OPEN_FILES, "How many files at the maximum InnoDB keeps open at the same time.", (gptr*) &innobase_open_files, (gptr*) &innobase_open_files, 0, GET_LONG, REQUIRED_ARG, 300L, 10L, ~0L, 0, 1L, 0}, Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables Order MySQL technical support from https://order.mysql.com/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]