The Bigdaddy updated was first mentioned by Matt Cutts on Novemember 30th in a blog comment where Matt noted “66.249.93.104 is the test data center (I think; as I get older, I get worse at IP addresses and phone numbers). If I do put out a call for feedback, the keyword will be bigdaddy…”
The Google Bigdaddy update is not an algorithm update but an infrastructure update according to Matt’s January 4th blog post where he posted “…new infrastructure at the Bigdaddy data center will let us tackle canonicalization, dupes, and redirects in a much better way going forward compared to the current Google infrastructure.”
On the same date Cutt’s did a post titled Bigdaddy Data Center where he did some question and answers.
Brett and WMW normally name updates. But this is neither an update nor a data refresh; this is new infrastructure…
It has some new infrastructure, not just better algorithms or different data. Most of the changes are under the hood, enough so that an average user might not even notice any difference in this iteration…
And the changes on Bigdaddy are relatively subtle (less ranking changes and more infrastructure changes). Most of the changes are under the hood, and this infrastructure prepares the framework for future improvements throughout the year.
The lastest update on Bigdaddy was the 1st of February where he offers a time table for datacenter conversions.
Remember that Bigdaddy involves new infrastructure and is not just a data push or algorithm update. Don’t take it as a promise, but I’d expect a new data center to be converted to Bigdaddy roughly every 10 days or so.