Depends on your disk setup. Remember a table space is a virtual filesystem that sits on top of the OS. Having one large file and chopping a contiguous block of the disk out enables better seeks as well as caching if the file doesn't bust the system cache. In your case it will. One file needs to be autoextended else your application will run into errors once the data needs to grow pass the tablespace.
Having multiple table spaces on different spindles enable the data to be segmented a bit more getting a few more bits of speed, but at the possible detriment of needed to access both separate data spaces if the data requested spans multiple files. In essence I have found that using multiple table spaces is best used when the disk is starting to fill up and I need to put the data on a different disk. You'll get a constant boost in performance if you put the innodb log files on a different spindle or set of spindles as your data file. -----Original Message----- From: Dave Juntgen [mailto:[EMAIL PROTECTED] Sent: Monday, December 06, 2004 6:30 AM To: [EMAIL PROTECTED] Subject: InnoDB tablespace Question. Hello! I have what seems to be a trivial question, but have not been able to find a definite answer and your help would be greatly appreciated. Question: When creating InnoDB table spaces, are there any advantages to using multi table spaces for each table or is it better to create a few large table spaces for all tables? If the latter, then is it best to create a very large table space, say 30G, (my OS supports LFS) rather then using the auto extend feature for table spaces in InnoDB? What is the over head of the InnoDB auto extend? Thanks! --Dave J. David W. Juntgen Medical Informatics Engineering Inc. Phone: 260.459.6270 Fax : 260.459.6271 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
