On Wed, Aug 13, 2003 at 04:07:24PM -0500, sean peters wrote: > Hi all, i've been weighing the pros and cons of running multiple concurrent > mysqld's on one server, to have better control over what databases are on > what physical disks. > > System: 4 processor sun box running solaris with eighteen 36Gb drives. > > The situation is that i have a bunch of databases on one server that can all > be classified as either external use or internal use. The internal use > databases are consistently hit pretty hard, and we want this to have minimal > impact on the external use databases. Currently we're using 64 index MyISAM > tables, and with carefully choosing mount points for various physical > devices, we have the databases separated as we want them. > > It is my understanding that with InnoDB, all tables are put into the > configured InnoDB file(s) together, which would violate what i am trying to > accomplish. > > The only solution i have come up with to control the physical location of > InnoDB databases is to run multiple mysqld servers, each one with its InnoDB > files on the desired device. > > Has anyone experienced any success or failure with this sort of configuration? > > This is the only reason holding us back from using InnoDB tables for this > server. (we're using them on other machines)
If you can wait a month or so, Heikki is supposed to have that fixed in InnoDB soon. So you'll be able to have more control over which data lives in which tablespaces. -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.13: up 12 days, processed 466,715,070 queries (443/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
