Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: open
The dns rotation learning disability thing amazes me too. Aaaaaaaaaannnyway...
We noticed this morning that the cached pages in -sj (which, until yesterday, weren't there), are now in place. Oddly, for some sites the cached data finally visible in -sj are inconsistent with the summary data displayed in the SERP's (the cached data appears fresh, while in some cases the summary blurbs in the SERP's are still from the Feb crawl).
Also, I know others have said they are seeing -sj from time to time at G partner sites, but we have yet to see that, despite hundreds of refreshes plus Web access from multiple remote terminals. We have only seen -fi appearing, along with the other 7 data centers not including -sj. Maybe it's just an odd coincidence.
However, another thought here is that they weren't letting the -sj data center filter out to the Web as they were the other 8, because the caches weren't there yet. Perhaps now that they're in, the -sj data will become more widely visible?
Just a thought. Won't make sense if I'm wrong about the -sj not appearing much...
I'm in Russia
By the way, it actually makes no difference where you are.
The update is happening when all the datacentres are "updating" - oddly enough!
Currently, that's not the case - as checking the IP address ranges for google will show those who actually understand how googles DNS system works. If you don't understand it, please stop posting to say "the update has started".
I've noticed the same. It's odd. GG seemed convinced that -sj would form the basis of the new index too. I'm getting the feeling he may be wrong on that one.
Or for some mad reason they are giving Yahoo! and aol something else. But that wouldn't really make sense either, unless they both specifically asked for that.
The dns rotation learning disability thing amazes me too.
Im sure Google is using alot more advanced techniques than simple DNS round robin rotation.
Its more likely a full blown content switching system that dynamically switches your query to the datacenter experiencing the least load at the instant you connect and/or execute your query, combined with other geographical and reachability paramaters.
[edited by: mrbrad at 1:53 pm (utc) on May 14, 2003]