Forum Moderators: Robert Charlton & goodroi
I don't know why I find it so funny.. But I do. Although this should reinforce the idea that this are distinct and non-related changes for those who seem to believe otherwise.
We will likely see some of Jagger 3 on some dc's before Jagger 2 has gotten to all of them.
Matt Said,
November 3, 2005 @ 1:39 pmLet’s see. Multiple data centers are now showing Jagger2, but I don’t think every data center is. I believe Jagger2 is at the cluster of data centers that includes 66.102.9.104. Stephen, I don’t think we support crawl-delay in robots.txt. But you might check out sitemaps–it might allow you more control.
Paul, the objective of Jagger is to improve our index results. The three stages are actually three independent launches.
urdudesamy, there are some Jagger1-related changes going on at 66.102.7.104.
Ahhhh, the DC I mentioned, 66.102.11.99, is showing the same results as above mention by MC. At least I sort of got the real Jagger 2 pegged. Everything will move from there. I still think I know the direction this is headed.
Hi Folks
Just for the benifit of our new kind fellow members.
Jagger Update, which was announced officially on 18 October 2005, but which might have started already on 22nd September 2005, is divided to 3 individual separate stages:
- Jagger1 (PR & Backlinks update)
- Jagger2 (dealing with spam issues)
- Jagger3 (dealing with index issues including canonicals and maybe supplementals issues)
In Matt's own words:
"Jagger1, Jagger2, and Jagger3 are mostly independent changes, but they�re occurring closely enough in time (plus they interact to some degree) that it�s clearer just to act as if they were one update for feedback purposes."
Which means, IMO, that Jagger3, in order to start, it doesn't need to wait for Jagger1 or Jagger2 to spread to all the DCs.
I hope this helps.
I think Mozilla Googlebot gave up when it kept recieving Can not connect to Database pages.
I was getting 10-20 hits per second for sustained periods, that is extremely high isnt it? - Or should I quiz my hosts a bit more.
Can you imagine if Microsoft, Oracle, Sun, or any other software giants released a product that was so poorly finished. I find it truely shocking that Google would release such horrible results into just one Datacenter, and more critically, roll out these unfinished Jagger's to all datacenters.
It is just my opinion that these pre-Jagger3 results are horrible. But it seems as if Google's representives in GG and Matt "Like a Knife" Cutts, state that we are in part 2 of a multi-phase rollout of a new index.
I understand that the index is in constant flux, but after all of this time, don't you think they'd learn to test the results? The concept of a beta is not a new concept. Please forward this url to someone important at google....Learn about Beta Testing [en.wikipedia.org]
Rolling out a half cooked pizza never tastes good. This is the type of thing a tiny, no-budget developer does, because its all that can be done.
Truely Shocking
I think that Google may want to buy MSN's index/results, just until Google can work out the kinks. IMHO
[edited by: greenfrog at 10:57 pm (utc) on Nov. 3, 2005]
We are getting worked real hard by both G and Teoma.
[edited by: Yippee at 11:00 pm (utc) on Nov. 3, 2005]
Running the link analysis alone on all their data must be a stupendous task. Maybe they had to rethink...