f246b8f2d7
noticesWithFriends is turning out to be one of our most expensive queries. The join is costly, and this method is hit over and over and over by desktop clients and other API users. So, I've added a first pass at caching the results. I store a "window" of notices -- equal to the first 3 pages of notices, plus one for pagination -- in the memcached cache. If with-friends notices are requests, I fetch the whole window out of the cache and grab the slice requested. If the requested notices are outside the window, we just do the query. If there's nothing in the cache, we request the window and store it, then return a slice. I had to add a NoticeWrapper class that works like DB_DataObject (well, just the fetch() part...) but just holds an array of notices instead of a DB cursor. Finally, saving a new notice blows away the caches for subscribed users. darcs-hash:20080915065616-84dde-1b1e814c2294498a10b763b779cbb62c3f96aa84.gz |
||
---|---|---|
.. | ||
action.php | ||
common.php | ||
daemon.php | ||
deleteaction.php | ||
gallery.php | ||
jabber.php | ||
language.php | ||
mail.php | ||
noticewrapper.php | ||
oauthstore.php | ||
omb.php | ||
openid.php | ||
queuehandler.php | ||
rssaction.php | ||
searchaction.php | ||
settingsaction.php | ||
stream.php | ||
subs.php | ||
theme.php | ||
twitterapi.php | ||
util.php | ||
xmppqueuehandler.php |