The raid function is not useful (that's to get around the 2GB filesize limit on certain OS). I think it's a misleading function (I think it should be called RAIF - Redundant Array of Inexpensive Files).
I use RAID 1 (hardware) scsi and my load looks to be processor bound (believe it or not) with a dual processor machine. I think that unless you are using a load that requires a quad processor machine, scsi160 drives on a raid card are fast enough, and hence there is no requirement for separate disks. If you must have separate files, I can only assume that there is an undocumented way to create a database in a specified tablespace. -----Original Message----- From: Brent Baisley [mailto:[EMAIL PROTECTED]] Sent: Monday, August 19, 2002 2:54 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: InnoDB and disk geometry You might want to lookup MySQL and RAID. MySQL does support a database RAID setup. This confused me early on because I kept thinking of disk based RAID, but this is database based RAID. I haven't used it yet, so I can't help you any more that that. Hope it helps a little. On Thursday, August 15, 2002, at 08:38 PM, [EMAIL PROTECTED] wrote: > A problem I have with InnoDB tables, which forced me to use MyISAM > tables in > a recent project, is as follows: > > (I am running MySQL on Solaris, not that it matters much for this > problem.) > > With MyISAM tables, I can easily get different databases to reside on > separate physical drives. > > The base directory for database files is /var/mysql/ > Then I mounted a drive at /var/mysql/db_a > and another at /var/mysql/db_b > > for instance. Then databases by the names "db_a" and "db_b" reside on > different physical drives. > > But with InnoDB, you specify a tablespace file(s) and then the database > you > create go into > those files. I cant figure out any reasonable way to tie specific > databases > to specific drives, > except by running a mysqld server for each drive I want a database on. > For large databases, proper planning of disk geometry can have a > significant > effect > on performance. I very much like InnoDB, but can't seem to get around > this > problem. > > Any insight would be greatly appreciated. > > sean peters > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > Before posting, please check: > http://www.mysql.com/manual.php (the manual) > http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <mysql-unsubscribe- > [EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > -- Brent Baisley Systems Architect Landover Associates, Inc. Search & Advisory Services for Advanced Technology Environments p: 212.759.6400/800.759.0577 --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
