And your base does belong to me :)
I don't do 250 but I like 100. I hate 50! I'm with you Xena, I want my 100 back! I asked John for it a couple of days ago on another thread and haven't yet heard back.
Oh yeah! Stune my beeber, baby!
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]
Have you thought to blame George Bush yet?
LOL!!!
mock lol
Try opening five browser windows at once. That should fix the problem.
If that doesn't work, then just run your monitor through with your sword!