Hello.
In my opinion, if you're unable to put InnoDB files on different disks there is no sense to use separate files. Even more - using the raw partition for InnoDB might increase a performance. See: http://dev.mysql.com/doc/mysql/en/innodb-raw-devices.html However, if you prefer many files, you may want to use per-table tablespace. See: http://dev.mysql.com/doc/mysql/en/multiple-tablespaces.html Richard F. Rebel wrote: > > > Hello, > > I was wondering if anyone had any knowledge to share regarding creating > many 2GB innodb table space files, vs creating a few 100GB ones. > > It has been my habit to create many smaller for several reasons, > including nfs clients/servers or utlities which don't reliably copy/ > back them up. > > Does this slow things down? I am about to create 1TB worth of InnoDB > table spaces and would really appreciate others perspecitves. > > Thanks! > > Richard > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
