#UPDATE 2012-08-20 11:18 EDT

#UPDATE 2012-08-20 11:36 EDT

UPDATE 2012-08-20 11:18 EDT

UPDATE 2012-08-20 11:36 EDT

I wrote about before : Benefits of table level locking

• Feb 12, 2011 : How do you tune MySQL for a heavy InnoDB workload?
• Jan 18, 2012 : Insert-heavy InnoDB table won't use all my CPU
• Jul 04, 2012 : Capabilities of InnoDB INSERT Performance
• Aug 17, 2012 : When to switch from MyISAM to InnoDB?

I wrote about before : Benefits of table level locking

• Feb 12, 2011 : How do you tune MySQL for a heavy InnoDB workload?
• Jan 18, 2012 : Insert-heavy InnoDB table won't use all my CPU
• Jul 04, 2012 : Capabilities of InnoDB INSERT Performance
• Aug 17, 2012 : When to switch from MyISAM to InnoDB?

#UPDATE 2012-08-20 11:36 EDT

If the read traffic is hindering your INSERT over UPDATE LOW_PRIOIRTY situation, I would have to recommend switching your MyISAM table to InnoDB. In fact, InnoDB can be tuned for performing heavy INSERTs. Please see my posts about tuning InnoDB for this purpose:

• Feb 12, 2011 : How do you tune MySQL for a heavy InnoDB workload?
• Jan 18, 2012 : Insert-heavy InnoDB table won't use all my CPU
• Jul 04, 2012 : Capabilities of InnoDB INSERT Performance
• Aug 17, 2012 : When to switch from MyISAM to InnoDB?