pending #varpull changes
NOTICE: The #varpull extension will be changing!
I am making a major change to #varpull that will improve performance that could impact the accuracy of list pages such as LotS/items/Officers.
This change will leverage memcached on the server side to store article text so that subsequent queries to an article over a period of time do not query the article. This will drastically improve performance on large pages such as LotS/items/Officers.
Accuracy of list pages may be impacted as long as the page lives in memcached. This is pretty much a non-issue though, but should be advised that the cache may take longer to update when changes are made. New items added to the list should be unaffected, unless their source article is updated prior to the cache in memcached expiring.
Changes to #varpull are now live and varpull is correctly pulling data from memcached.
We should see significant improvement on several pages with multiple calls to varpull.
It is important to note that there are 2 different types of cache involving memcached. Each page generation is stored in memcached for approximately 2 minutes. #varpull caches target article text which it retrieves for 15 minutes. So it may take up to 15 minutes for a item table to update even if you forcibly save the item table page. As a bonus though, the page will pull from cache with minor updates so the 2 minute page cache will be generated faster since it will pull its data from the #varpull cache.
Now we can safely continue bombarding #varpull with an obscene number of requests without worrying too much about the performance hit.