Re: Q1. What would run faster?
Mikhail Berman [EMAIL PROTECTED] writes: Dear List, I am looking to see what the List thinks about this question. If we to run the same query that needs tmp table to be open to get an answer. * on a server with * and without an RAID array, the rest of hardware would not change as much as possible. Where this query would run faster? For disk intense applications, regardless if it's a database or some other application, a proper RAID setup will of course run faster. It also depends on what kind of RAID you are using, and how well the RAID implementation (typically the RAID controller) works. /David -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
How can I get my disk space back?
I have a really simple (two tables, one relation) but big (~70 GB) innodb database containing rather dynamic data. After deleting lots of records from the tables, the innodb data files still take the same amount of disk space as before. What is the correct way of freeing the disk space? The general solution seems to be alter table tablename type=innodb which completely rebuilds the table, but this is not acceptable because: a) It locks the table during the operation making it unavailable to other clients. b) It involves copying the table, taking twice the disk space during the operation - disk space that I do not have. Is there another way of doing this? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: How can I get my disk space back?
Barry [EMAIL PROTECTED] writes: David Israelsson schrieb: I have a really simple (two tables, one relation) but big (~70 GB) innodb database containing rather dynamic data. After deleting lots of records from the tables, the innodb data files still take the same amount of disk space as before. What is the correct way of freeing the disk space? The general solution seems to be alter table tablename type=innodb which completely rebuilds the table, but this is not acceptable because: a) It locks the table during the operation making it unavailable to other clients. b) It involves copying the table, taking twice the disk space during the operation - disk space that I do not have. Is there another way of doing this? Probably OPTIMIZE helps here I wish I was that lucky. According to the documentation, OPTIMIZE for InnoDB tables is mapped to ALTER TABLE. This is also exactly my experiences after actually trying it. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
