Bryan,
> One thing to keep in mind, due to a lapse in our judgement at the
> time, this itemexperiencelog table serves as both a current state
> table, and a log table. Therefore, it potentially has multiple
> redundant entries, but we typically only look at the most recent entry
> to figure out the state of the current item.
Oh, I see. It thinks that it'll need to pull 260,000 redundant rows in
order to get 1800 unique ones. Only it's wrong; you're only pulling
about 4000.
Try increasing some stats still further: itemexperiencelog.visitorid and
visitors.user_id both to 500.
--Josh