Forum Moderators: Robert Charlton & goodroi
"Okay, either I'm going nuts and seeing things or Google is playing tricks on me."
No you are not going nuts. I think that its Google which has deployed something that makes us go nuts.
Please welcome Google Virtual Datacenters :-)
I saw serps today which I couldn't see on any of the DCs that we know. Therefore I posted today msg #:149 about [google.sk...]
[edited by: Brett_Tabke at 2:25 pm (utc) on April 26, 2006]
And guess what....Again, these SERP's are GONE!
Thank God I do not have clients that I would have to report this stuff to.
Please welcome Google Virtual Datacenters :-)
Could VIRTUAL be the new Infrastruture?! My sites are virtually there and then virtually GONE! :>~
"Could VIRTUAL be the new Infrastruture?! My sites are virtually there and then virtually GONE! :>~"
I wouldn't be surprised of anything about that new infrastructure thing ;-)
Well I did try today to ping and tracert [google.sk...] once I saw the new unique serps. But I felt I was redirected to the wrong IP all the time. Because when run my test keywords on the IP I got, the serps was not the same as the new unique serps I saw first time.
Now.. a question to kind fellow members who understand servers/datacenters technically:
Is it possible to hide an IP or is it possible to redirect a ping/tracert query to another IP than the real one?
Thanks.
Bed time. Good night and God bless.
In a load balanced server environment, it is very easy to add and remove servers from "pools", for testing, upgrades, meaning at any time, they can take a server, or group of servers out of a pool, make changes, and then toss them back in the pool. They can also place a higher priority on some servers, so that other servers only start answering queries under heavier load conditions.
A datacenter IP might have many pools of servers, all hiding behind a single ip address, and you would never know, because the response to your query, would always be returned from a single datacenter IP.
Only Google knows for sure how their "Infrastructure" is exactly setup.
You could say Google is like a box of chocolates,,,,,,,, but I will not say it.
Back to Watching
WW_Watcher
Edited to add, these are also known as server farms, if you need more proccessing to handle a larger load, you just grow more servers, add more load balancers creating unlimited capacity.
Picture in your mind, a single ip address (datacenter AKA loadbalancer), which is load balanced to 5 more load balancers, each of which is supporting 5 more load balancers, each of which has 50 servers answering queries. Creating A 1250 server datacenter, for supporting queries for that region.(if I did my math right, never was good at math, but I was good at designing, building and supporting these kinds of enviroments for some very well known corporations).
Back to Watching
WW_Watcher
Is it possible to hide an IP or is it possible to redirect a ping/tracert query to another IP than the real one?
no it isn't possible for google to send you to a different IP. Google has to play by the rules with regards to DNS like the rest of the internet remember. Once an icmp (icmp=pings, traceroutes, path unreachables, etc) enteres their network is anyones guess.
Keep in mind, once you retrieve and IP address from a dns lookup to either ping google or to fetch a webpage the moment it enters their network they (or anyone for that matter) can send your request to anywhere or anything. your only barometers (really) are packet transit times and the fact that google wants to keep traffic as local to you as possible to keep their bandwidth bills down.
my birthday wish from google is a GWS header that tells some basic info about DC location and SERPs versioning or something. wouldn't that be swell?
Special thanks to our kind fellow emembers WW_Watcher and kilonox for taking the time to provide us with those much needed technical info.
So if I understood things correctly, there might be several servers hiding behind a single ip address of DCs.
Keeping in mind that different DCs get different data at different times (as per Matt Cutts), there is the "risk" that we wouldn't be able to really trace specific serps.
And it seems; that was exactly what happened for some of us yesterday. Personally, I saw the most wonderful serps on [google.sk...] , but I wasn't able to trace the specific server of the DC which contained those serps.
And that in turn confirm that the folks at the plex are able to produce good serps, but mightbe just testing and testing now all possibilities, and pick later the best of them.
And that lead me to say:
Google is still the best..better than all the rest :-)
Wish you all a great sunny day and a happy Google Datacenters Watching (including "Virtual" DCs Watching too).
Hi Folks
So now I have screen captured the new unique serps I was talking about yesterday but which I also see right now this morning on [google.sk...] .
When mouse hovers over cache it shows IP [66.249.93.104...]
when run tracert or ping, I get the same as above.
However, the serps on [66.249.93.104...] are very similar though aren't 100% the same as the serps on [google.sk...]
What a wonderful way to start this great day with. Trust me... life is wonderful.
Long Live.. Google Virtual Datacenters Watching :-)
The real question is... when?
How do I know?
Well, I have a query that returns 20 results on most DCs and more than 900 on 72.14.207.* and now also on google.sk too.
I also ran 10 other queries that I know the results for, and all 10 confirmed the "experimental" results. I could run another 40 or 50 queries, but I think 10 is more than enough confirmation.
Google could also be looking at the referring site or other request variables to cloak results. When you are asking for results at a specific IP, they may just randomize results to mess with your head.
I wonder if Google is playing with splitting ecommerce and research in a similar way that Yahoo Mindset does.
"Google could also be looking at the referring site or other request variables to cloak results. When you are asking for results at a specific IP, they may just randomize results to mess with your head."
In my case, Google is mostly showing me results I like but they don't exist on any of the DCs we know!
Its therefore Virtual DCs or DCs hiding behind the same IP though showing different serps than the rest of the DCs under the same IP.
Talking about the new infrastructure. What else are they going to serve for us poor Google Datacenters Watchers :-)
Good evening Folks
My academic background is a Chemist. And in chemistry its rather important that the process and products a chemist develops should be reproducible. Otherwise they are just useless.
If we attempt to apply chemistry standards on Google's deployment of BigDaddy, new infrastructure, the everflux of the serps, any jr. chemist will tell you that BigDaddy process and Google's current serps are useless. Unreproducible product of Zero value.
But we know that chemistry standards can't be applied to Google and its processes and products. Therefore we can't just say that current serps are useless because they are unreproducible.
Maybe you have a term which describe best the current Google's infrastructure and its serps, and for that I thank you in advance.
Good night and God bless.
Not sure I'm keen on the end result either...
Shake up imminent? I mean, this surely can't be it?
As per your request to keep you updated, SERPS changed across the test DCs and the main .com this morning in my sector. Has become much more relevant, but still a little way to go I think before it's as good as it was.
And hasn't helped me personally one bit - lol :-)
Cheers
Simsi
I have noticed that if:
www.google.co.uk results show that [66.249.93.104...] (for instance) is the DC via the cache link...
Replacing www.google.co.uk with 66.249.93.104 in the search string produces entirely different results for our keywords.
In our case the www.google.co.uk are significantly worse than with the raw DC address.
This is the same with any DC google.co.uk may be using.
Why I wonder?
At the moment there look like there are 2 main sets of results in the datacenters, and for my keywords they are only a little different - [64.233.167.99...] is an example of one set and the other is [64.233.161.99....] I expect within 24 hours all the datacenters will be showing one of the other.
I really like the newest set of results, though I'm still seeing a few old pages and semi-irrelevant forum pages ranking relatively highly. Anyway, I think we're going to see some significant improvements over at Google in the next couple of weeks.
And I definitely agree that Google is using different load-balancing servers that are updated seperately. While this is occuring occasionally on some datacenters, most datacenters seem to update their servers at roughly the same time.
There is also the "experiment" over at 72.14.207.* too (but not there all the time though).
Same here Reseller. It's been that way for quite a while for me but it begin to conforn to other DC's in past 24 hours. Could start fluxing again. I rarely get results on default Google other than 72.14.203.104.
Good morning Folks
2 cups of warm delicious Danish Brand Cappuccino! Great start of a wonderful day. And never forget.. Its great to be a live.
I'm a big Matt Cutts fan and an ancient Google lover, no doubt about it. Not to forget that I'm a big GoogleGuy fan too, ya know :-)
Being a big fan of Matt and GG means also that I read their posts and spend some time "decoding" what they say.
Last year just after update Allegra in February, some of us on WebmasterWorld start mentioning the possibility of Google deploying Random Serps or Rotating Algos. Then we forgot all about the two terms.
Lately, I read few but very solid statements of my hero Matt confirming the fact that at present we should expect Random Serps. Matt wrote something in the directions:
- Different datacenters get different data at different times.
- Different centers can rank things differently.
And that means: Search results are dependent on which time of the day and which datacenter you hit. I.e no consistency in Google serps any more. I.e you get serps in random!
Well... I guess we have to live with those random serps from now on.
The good news is; your site ranking might drop within some hours of the day or on some datacenters, but it might rank well during other hours of the day and on other datacenters!
By that way, every site on the web would have its own 5 minutes of fame. Equal opportunity for all sites!
Long Live Google's Random Serps!
Long Live Google's Democracy!
Wish you all a great sunny day.
Google goes hand in hand with the word "Search" according to the general public. If they start noticing inconsistencies they are not going to pound their head against the wall until Google returns the result they are looking for. They will simply jump ship and Google will lose it's luster for the term "Search".
It seems that if different data centers have different data they should be expected to show different results.
But to spin this up into some idea that google is presenting random results is pure hyperbole. It is just flux and should be expected.
"All Cutts said was that different data centers get data at different times. And that they can rate sites differently."
And thats a very accurate definition of Random Serps!
Thanks!
"Google goes hand in hand with the word "Search" according to the general public. If they start noticing inconsistencies they are not going to pound their head against the wall until Google returns the result they are looking for. They will simply jump ship and Google will lose it's luster for the term "Search". "
Well... that have been the case since November-December 2005. I.e Google's serps have been in random for around 5-6 months. Have you heard any complaints from the general public ;-)
Google's Random Serps don't need to be something bad. Many publishers would be happy to see their sites ranking part-time instead of not ranking at all.
I'm just trying to find something posative about Google's Random Serps and adopt to them, as you might have noticed ;-)
