Site Caching
By Barry Ritholtz - November 14th, 2008, 6:59AM
Macro Notes
10 year bond yield/50% retracementPeter Boockvar
With the sharp drop in the 10 yr bond yield over the past month after touching 4%, the move has retraced almost 50% of the rise from the 2.5% level that occurred right after the FOMC announced a step up of their QE policy on March 18th and said they were going to start buying US Treasuries directly. The exact 50% retracement is 3.24% and to put this level in perspective look at the previous deflation scare (with the Fed in their Halloween masks feeding the scare) in 2002 and 2003 when the 10 yr bond yield dropped to 3.11%....
read more »
The Big Picture is proudly powered by
WordPress
Entries (RSS) and Comments (RSS).
Entries (RSS) and Comments (RSS).
November 14th, 2008 at 9:45 am
Whew! for some time this morning, the site was loading only the header and tabs with no content displayed below. Finally it’s back up.
November 14th, 2008 at 10:29 am
I noticed a dramatic load time difference almost immediately. I love the new site, Barry! The cafe is fantastic.
November 14th, 2008 at 11:28 am
I see you’re using WP-Cache. Definitely consider taking a look at WP-Super-Cache. it improves on WP-Cache by making it a ‘layered’ cache. Anonymous visitors are show static html copies of pages that are updated when new comments are posted or changes are made. It even stores them in compressed format, making it trivial for the web server to return the content (instead of having to compress it on the fly - it’s already in that format so the web server just serves it up). GREAT for stories with lots of comments.
Logged in users get handled by the normal WP-Cache system, allowing you to have dynamic sections, etc. in otherwise static cache copies. Some more load on the web server, but given that most of your visitors will NOT be logged in, worth it.
If you find a story of yours is on Digg, or some other site bringing loads of traffic (and comments) you can even flip WP-Super-Cache into lockdown mode where the pages won’t refresh on every comment - instead expiring every X minutes which you set - great way to handle a huge traffic spike.