250 results is putting an incredible strain on the database. I have a switch that allows me to put a hard limit on the number of results returned, and I'm playing around with different hard limits in order to find one reasonable. [50 seems to be it, btw.] However, this is temporary, I have more programming to do, I can cache more things, and we ARE under a heavier-than-average load. Hence, we're in "overload".
And, after running view counts for awhile, I found that I cannot do them in (quasi-)realtime without more programming. I am still recording views, just not displaying them.
[geek]
For those interested in the technical aspect of the later, I cannot perform concurrent UPDATEs and SELECTs on the same table. Every update blocks all selects, and that gums up the works. MySQL updates of MyISAM tables are table locked on update. :-( [But they do allow concurrent INSERTs and SELECTs--so it isn't all sucky.] I haven't investigated the other table types, it may be possible to use e.g. a heap table for just the counters that have been updated. I'd sync the counter table with the main table during the night for permanence. (Heap tables are RAM only--they vanish when the daemon/server goes down.) Or, I could do away with UPDATE and use INSERT on a table, and just sum the counts for a group of articles. Syncing during the night to remove rows. I have options. (BTW, I'd probably use Memcached to increment a per article counter so I don't have to do a GROUP operation for every article I want counts on, I'd just use the in-memory cache for the realtime reporting.)
[/geek]
Exactly what I figured!
;^)
THANKS TONS FOR *ALL* YOUR EFFORTS.
YOU THE BEST!
Haven't checked the stats lately. I should go see how many daily unique person hits we're getting!
I wonder how much the Swift Boat stuff is triggering it.
May your solutions be as brilliant as ever with half the usual stress and effort.
Can't find where to look up the stats. Maybe I've forgotten how.
Are daily etc. stats still available?
250 results is putting an incredible strain on the database.Okay, I can live with that. It's bound to happen, because FR is so darned popular, and also those of us on here pump up the volume on each of the 1000s (?) of threads posted every day. And we ping each other. And email each other.
50 is soooo Lame. It should be at least 100. That is what I use. Not working right now though. The place you could cut is on self search. There is no need for a lot of returns there. I would think 10 would be enough. But it takes me longer to read a thread if I have to keep hitting next every 50 posts. Especially since I often speed read to find content. 50 is nothing.
Thanks John.