We are using mysql-4.0.18, compiled from source with: ./configure --prefix=/usr/local/mysql --enable-thread-safe-client --enable-assembler --enable-local-infile --enable-largefile --with-mysqld-user=mysql --without-debug --with-innodb
A two-pronged question: First, in our experience, we don't see InnoDB striping across its tablespace files, we see it filling them sequentially. Therefore, we currently have our production db built with 400 x 1GB tablespaces, alternating across the two RAID arrays connected. Is there a way to make InnoDB stripe the tablespaces instead of using them in a concat fashion? This would enable us to use bigger tablespaces, and would pretty much invalidate the second question. Secondly, what is the max length of innodb_data_file_path? Currently, we've gone to the below to get a reasonable number of tablespaces small enough to have good performance: innodb_data_home_dir = /usr/local/mysql/var/ innodb_data_file_path = aa:1G;i2/ab:1G;ac:1G;i2/ad:1G;ae:1G;i2/af:1G;ag:1G;i2/ah:1G;ai:1G;i2/aj:1G;ak:1G;i2/al:1G;am:1G;i2/an:1G;ao:1G;..... Basically I need to know what the maximum length of this line is (I've had some problems with MySQL failing to start with an extremely long line, and would like an authoritative value to stay under). Thanks. -j -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
