Pete Freitag Pete Freitag

Insert Delayed with MySQL

Published on August 02, 2005
By Pete Freitag

I just discovered that MySQL has some handy optimization hints, and commands that you can pass in your SQL statements. Since there is a lot to cover with each tip, I will be posting them in separate blog entries. I have already written about the MySQL Query Cache optimization hints.

Delayed Inserts

You can delay INSERT's from happening until the table is free by using the DELAYED hint in your SQL statement. For example:

INSERT DELAYED INTO table (col) VALUES ('val');

The above SQL statement will return quickly, and it stores the insert statement in a memory queue until the table your inserting into is free from reads. This means that if there are multiple inserts in the queue they can be written in one block, which is a more optimal use of IO.

The downside to this is that it is not transactionally safe at all. You don't really know how long its going to take for your INSERT to happen. If the server crashes, or is forcefully shutdown you will loose your INSERTs. So don't use this on any critical information that would suck to loose.

One great use for the DELAYED keyword would be for storing web stats in a database. You don't want the client waiting for the stats to insert, and its not that big of a deal if you loose a few stats (for most people).

Status Variables

The following status variables can be used to monitor your delayed inserts:


You can get the values by running the SQL statement: SHOW STATUS

You can find more information about INSERT DELAYED in the MySQL Documentation.

mysql insert delayed performance sql optimization databases

Insert Delayed with MySQL was first published on August 02, 2005.

If you like reading about mysql, insert, delayed, performance, sql, optimization, or databases then you might also like:

Discuss / Follow me on Twitter ↯


Pete: I'm gonna bear this one in mind for the future. Right now, JournURL's referrer logging probably doesn't need it (particularly after reading the docs), but it could become a big deal down the road.

Thanks for the pointer!
by Roger Benningfield on 08/03/2005 at 1:25:37 AM UTC