, It will take only
> 2 min to drop the table.
>
> Thanks,
> Dilipkumar
>
>
>
> -Original Message-
> From: Krishna Chandra Prajapati [mailto:prajapat...@gmail.com]
> Sent: Tuesday, November 10, 2009 12:04 AM
> To: Michael Dykman
> Cc: MySQL
> Subject: R
: DROP TABLE TOOK 39MIN
Hi Michael,
Already using innodb_file_per_table.
Krishna
On Mon, Nov 9, 2009 at 9:39 PM, Michael Dykman
wrote:
> Under InnoDb, you could use file-per-table which would have
> significantly reduced the inter-dependencies.. given the large data
> size and heav
Hi Michael,
Already using innodb_file_per_table.
Krishna
On Mon, Nov 9, 2009 at 9:39 PM, Michael Dykman wrote:
> Under InnoDb, you could use file-per-table which would have
> significantly reduced the inter-dependencies.. given the large data
> size and heavy I/O you report, it might be a wis
Under InnoDb, you could use file-per-table which would have
significantly reduced the inter-dependencies.. given the large data
size and heavy I/O you report, it might be a wise way to go.
- michael dykman
On Mon, Nov 9, 2009 at 3:41 AM, Johan De Meersman wrote:
> Presumably because you are r
Presumably because you are removing 189 gigabyte of data and 549 gigabyte of
indexes, all of which need to be marked as deleted in your innodb file. I/O
is rather expensive :-)
On MyISAM this would have been close to instantaneous (as you probably
expected), because the datafile is used only for t
Hi Experts,
I have a crm(customer resource management) table which contains 654 million
records. Dropping table took 39min. In addition to this other queries become
very slow and they are not associated with bkp_mtlog any way. why?
mysql> show table status like 'bkp_mtlog';
+---++
