On Wed, Jan 29, 2003 at 03:55:16PM -0800, Brion
Vibber wrote:
On mer, 2003-01-29 at 14:15, Jan Hidders wrote:
Not necessarily, row level locking causes sometimes a *lot* more overhead
and can block *more* than table level locking. I assume you have read the
manual but for good measure I will quote the relevant part anyway:
If you have concrete suggestions on how to reform our code, I'd *love*
to hear them. I say this in all seriousness; I freely admit that I'm new
at this database stuff, and am unsure of the best course of action.
Ok, sorry for being critical in an unhelpful way. But I would still want to
know if there was a concrete problem that you wanted to solve with row-level
locking, or would going back to full MyISAM be an option? My gut feeling is
that row locking really doesn't help much because our access patterns are a
lot of small reads (fetching pages), a few big reads (recent changes et
cetera) and relatively rare small updates that don't mind if they have to
wait a few seconds.
Well, an update (counter increment) comes with every page view, and we
often have several edits per minute.