Re: How to plan the Tablespace in a huge mysql?
I expect the data size is no more then 1.5TB. Why don't you like to let tablespace auto grow? Is it performace issue or not? If I create ten innodb_data_file and each size of innodb_data_file is 50G, dose some issues must be take care? Because the 50G is really very big for a file, I never do it. Regards, proace On Tue, 15 Feb 2005 07:27:42 -0800, Gary Richardson [EMAIL PROTECTED] wrote: My preference is to use innodb_data_file. If everything is InnoDB, I would probably create 25G or 50G files until you've created enough to hold all the data plus enough for growth. Do you know specifically how big the data is? I don't like to let my table space autogrow, so I have monitors watching the free innodb space. If it gets tight, I manually add more space. On Tue, 15 Feb 2005 20:25:36 +0800, proace Tsai [EMAIL PROTECTED] wrote: Hello: The mysql server is estimated to be as follows, 1. two servers, one is master and the other is slaves (replication) 2. two databases in mysql 3. 513 tables in each database 4. about 300 rows in each table 5. about 2T disk space for each server using SAN Storage 6. backup database periodically The running environment is follows, Server: Dual Intel Xeon 3.2G with 4G DDR2 Memory. OS: FreeBSD 5.3-RELEASE MySQL: 4.1 branch Operation: 70 ~ 80% operation is query (select statement) According to the above terms, how to plan the Tablespace in the mysql server? Using raw devices for the tablespace or innodb_data_file? ( How many Tablespace do I create? ) or using innodb_data_file with innodb_file_per_table? Regards, proace. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: How to plan the Tablespace in a huge mysql?
I've always figured that if your tablespaces are tight enough to autoextend, you're going to take a performance hit. InnoDB uses the tablespace for some transaction/rolebacks -- if you have a large transaction going through it will be slowed down by an autoextend operation. Plus, once you're there, you're probably going to be always autoextending. I can't find anything 'official' that says this, so I could be talking straight out of butt. If you're talking about autoextending files on a 1.5TB database, you're going to have 50GB files anyway. I'd sooner control it than let it grow wildly. On Wed, 16 Feb 2005 19:44:56 +0800, proace [EMAIL PROTECTED] wrote: I expect the data size is no more then 1.5TB. Why don't you like to let tablespace auto grow? Is it performace issue or not? If I create ten innodb_data_file and each size of innodb_data_file is 50G, dose some issues must be take care? Because the 50G is really very big for a file, I never do it. Regards, proace On Tue, 15 Feb 2005 07:27:42 -0800, Gary Richardson [EMAIL PROTECTED] wrote: My preference is to use innodb_data_file. If everything is InnoDB, I would probably create 25G or 50G files until you've created enough to hold all the data plus enough for growth. Do you know specifically how big the data is? I don't like to let my table space autogrow, so I have monitors watching the free innodb space. If it gets tight, I manually add more space. On Tue, 15 Feb 2005 20:25:36 +0800, proace Tsai [EMAIL PROTECTED] wrote: Hello: The mysql server is estimated to be as follows, 1. two servers, one is master and the other is slaves (replication) 2. two databases in mysql 3. 513 tables in each database 4. about 300 rows in each table 5. about 2T disk space for each server using SAN Storage 6. backup database periodically The running environment is follows, Server: Dual Intel Xeon 3.2G with 4G DDR2 Memory. OS: FreeBSD 5.3-RELEASE MySQL: 4.1 branch Operation: 70 ~ 80% operation is query (select statement) According to the above terms, how to plan the Tablespace in the mysql server? Using raw devices for the tablespace or innodb_data_file? ( How many Tablespace do I create? ) or using innodb_data_file with innodb_file_per_table? Regards, proace. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
How to plan the Tablespace in a huge mysql?
Hello: The mysql server is estimated to be as follows, 1. two servers, one is master and the other is slaves (replication) 2. two databases in mysql 3. 513 tables in each database 4. about 300 rows in each table 5. about 2T disk space for each server using SAN Storage 6. backup database periodically The running environment is follows, Server: Dual Intel Xeon 3.2G with 4G DDR2 Memory. OS: FreeBSD 5.3-RELEASE MySQL: 4.1 branch Operation: 70 ~ 80% operation is query (select statement) According to the above terms, how to plan the Tablespace in the mysql server? Using raw devices for the tablespace or innodb_data_file? ( How many Tablespace do I create? ) or using innodb_data_file with innodb_file_per_table? Regards, proace. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
