Bug #65615 after truncating the table,data insert is slow

Submitted: 14 Jun 2012 11:32 Modified: 15 Jun 2012 3:57
Reporter: tatsuya sano Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.6.5 m8 OS:Linux (CentOS5.8 32bit)
Assigned to: CPU Architecture:Any
Tags: truncate

[14 Jun 2012 11:32] tatsuya sano
Description:
after truncating the table,data insert is slow.
And This problem occurred at innodb.

How to repeat:
No1.create table 
 CREATE TABLE `t1` (
   `id` int(11) NOT NULL default '0',
   PRIMARY KEY  (`id`)
 ) ENGINE=InnoDB DEFAULT CHARSET=utf8;

No2.data insert
 any big data inserts to t1.
 ex.insert into t1 select id from *;

No3.truncate table 
 truncate table t1;

No4.data insert
 any big data inserts to t1.
 ex.insert into t1 select id from *;

-- No.4 is about 5 times slower than No.2 at my environment.
[14 Jun 2012 11:44] Valeriy Kravchuk
Please, send your my.cnf file content. I wonder if innodb_file_per_table is set. This may be similar to bug #59783.
[15 Jun 2012 1:38] tatsuya sano
my.cnf file

Attachment: bug-data-65615.txt (text/plain), 5.40 KiB.

[15 Jun 2012 2:48] tatsuya sano
I checked the bug # 59783, I thought it was the same problem.
I tried the same test at MySQL5.5.25, this problem has been fixed.

In MySQL5.6.6, there is no problem because it is scheduled for this fix.

Thank you so much.
[15 Jun 2012 3:57] tatsuya sano
changed status.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.