No subject

Now, we have a *lot* of SELECTs that involve the cur table. We also have
a *lot* of UPDATEs that involve the cur table -- on every page load we
increment some row's cur_count. Should be quick, but since it has to
wait until any other SELECTs are done, and any later SELECTs have to
wait until *it* is done...

If I understand correctly, this means we can get stuck in a cascade of
waiting for the previous selects to finish before we get anything, as if
we were serving a gazillion pages all through from one pipe.

I've made the various counter update queries LOW_PRIORITY; we'll see if
that helps any.

I think it was once suggested that breaking the page counters to a
separate table (two numeric columns, ID and count) might be a good idea.

-- brion vibber (brion @ pobox.com)