1. Peter Zaitsev ran some tests which suggested that multiple .ibd files are
not slower than one ibdata file. But it will depend on the OS version. Some
OS'es may have bad fsync() implementation, which can cause slowdown with a
large number of files.
2. Clustering? If you mean the fact that InnoDB stores the row data in the
PRIMARY KEY index (= clustered index), that is also true for .ibd files. The
only thing that changes is the file, not internal storage formats of tables.
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - hot backup tool for InnoDB which also backs up MyISAM
From: Chris Nolan (chris@stripped)
Subject: Re: MySQL/InnoDB-4.0.16 is released + sneak peek of 4.1.1
View this article only
Date: 2003-10-22 09:19:19 PST
Multiple table spaces eh? Funky! Of course, as you've no doubt become
aware, I am one of these annoying
people that has many questions to ask the list the moment something like
this comes along! Please feel
free to ignore these questions though, as we're all hanging out for 4.1.1.
1. Are there any performance implications (either way) with the use of
multiple table spaces? Are there any
other implications that you think are worthy of note (other than the
obviously easier backup options).
2. Is there any way that clustering can still happen with multiple table