When to use mysqldump with '--no-autocommit'? My benchmark shows slower restore
With autocommit=1, each INSERT will be committed before moving on to the next.  There is less overhead.  But, if the server crashes, the table will be half built because some INSERTs will be committed; some won't.

With

SET autocommit=0;
INSERT...
INSERT...
...
commit;


it will put all the info into a redo log for the entire table.  For large tables, this is more overhead.  Even for a tiny tables (only one INSERT), it might be a little slower due to the extra two statements.