wouldn't it be easier (and have the same effect) if you just wrapped 100 statements (or say 60 seconds) of delay-able INSERTS into a transaction with the correct isolation value set?
or use INSERT DELAYED and let the database do it itself.
or use INSERT DELAYED and let the database do it itself.
If you configure innodb correctly it comes down how much IO you can do on your log fs, to make sure you can sustain some update rate to this sequential log. Then nest is the IO to the db fs, so you can sustain the rate of the flushes. You can tune some of this much better with some percona mysql patches. Innodb does insert batching for you to minimize IO, and if you are doing updates to the same data it may even buffer the changes in buffer pool.