Why is MySQL InnoDB insert so slow?

by

InnoDB has transaction support, you’re not using explicit transactions so innoDB has to do a commit after each statement (“performs a log flush to disk for every insert”).

Execute this command before your loop:

START TRANSACTION

and this after you loop

COMMIT

More Related Contents:

  1. MyISAM versus InnoDB [closed]
  2. Is there a REAL performance difference between INT and VARCHAR primary keys?
  3. UUID performance in MySQL?
  4. MYSQL OR vs IN performance
  5. MySQL foreign key constraints, cascade delete
  6. How do I see all foreign keys to a table or column?
  7. How to Perform an UPSERT so that I can use both new and old values in update part
  8. JDBC batch insert performance
  9. TINYTEXT, TEXT, MEDIUMTEXT, and LONGTEXT maximum storage sizes
  10. SQL Performance UNION vs OR
  11. Howto: Clean a mysql InnoDB storage engine?
  12. MySQL InnoDB not releasing disk space after deleting data rows from table
  13. MySQL vs MongoDB 1000 reads
  14. How to convert all tables from MyISAM into InnoDB?
  15. MySQL InnoDB foreign key between different databases
  16. What is better in MYSQL count(*) or count(1)?
  17. Bogus foreign key constraint fail
  18. What is MySQL’s default ON DELETE behavior?
  19. How to optimize COUNT(*) performance on InnoDB by using index
  20. How do I repair an InnoDB table?
  21. How to enable INNODB in mysql
  22. How to disable index in innodb
  23. MySQL: Inner join vs Where [duplicate]
  24. Higher cardinality column first in an index when involving a range?
  25. How to regex in a MySQL query
  26. Why doesn’t MySQL’s MyISAM engine support Foreign keys?
  27. MySQL: Many tables or many databases?
  28. sql group by versus distinct
  29. Database corruption with MariaDB : Table doesn’t exist in engine
  30. Should I always prefer MySQL InnoDB over MyISAM?

Leave a Comment