Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

Update Jagger - Part 2

         

Brett_Tabke

1:08 am on Nov 2, 2005 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Continued from
[webmasterworld.com...]

followgreg

8:57 pm on Nov 3, 2005 (gmt 0)

10+ Year Member



Googleguy,

Just to follow up, I'd like to say that the misbehaving website was removed, that was pretty fast great work!
However the "SEO company" (the real responsible) keeps on spreading their spam and cheats, I think that this one is the one to target because they convince their customers, not very knowledgeable, that it is ok to hide text, build cloaking pages etc...
I just submitted some more spam from them, on more competitive terms.

I suppose that it's going to take some time considering the HUGE amount of cheats only from that company across all industries and all continents, it feels a little like they are playing Google isn't it? With their URL embedded in their cloaking pages :)

Good investigation!

Dayo_UK

8:59 pm on Nov 3, 2005 (gmt 0)



>>>It's been hitting 2-3 pages per second on our site for the past several hours

I think my site could handle that - but 20 a second for a sustain period.

Yippee

9:00 pm on Nov 3, 2005 (gmt 0)

10+ Year Member



Are you running the site on an e-Machine? You should upgrade you know :) Also, you probably shouldn't be posting here right now considering the resource consumption and all.

[edited by: Yippee at 9:05 pm (utc) on Nov. 3, 2005]

Dayo_UK

9:04 pm on Nov 3, 2005 (gmt 0)



Lol - not hosted at home.

20 hit per second for a sustain period works out at 72,000 page requests an hour.

When my site was doing well I only recieved say 500 visitors an hour.

walkman

9:08 pm on Nov 3, 2005 (gmt 0)



>>> I think NEO was an idiot... He could have been taking X for cryin out loud!

some would say that people cut and pasting TOTALLY unrelated comments on a Google update thread are...well you get the point :)

Yippee

9:09 pm on Nov 3, 2005 (gmt 0)

10+ Year Member



Well, good luck in keeping up your system. This is a critical time for you to get crawled even though the number of hits is not reasonable. Hope it goes well.

Eazygoin

9:11 pm on Nov 3, 2005 (gmt 0)

10+ Year Member



Matt has posted on his blog if anyones interested....reveals quite a lot!

Yippee

9:11 pm on Nov 3, 2005 (gmt 0)

10+ Year Member



No, I don't get the point walkman... Why don't you tell me, and the rest of everyone here that has diverged what you meant by that statement...

I have yet to call you or anyone else names, let's maintain the peace please ;)

[edited by: Yippee at 9:13 pm (utc) on Nov. 3, 2005]

thecaptainandcookie

9:12 pm on Nov 3, 2005 (gmt 0)



From Matt Cutts, Today, November 3, 2005 @ 1:39 pm
"Let’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."

[mattcutts.com ]

[edited by: thecaptainandcookie at 9:15 pm (utc) on Nov. 3, 2005]

Dayo_UK

9:13 pm on Nov 3, 2005 (gmt 0)



Anyway, database is now reloaded and I have changed a primary key around (as it probably was not best optimized anyway)

Even with this change it is unlikely to be able to survive that type of crawling (IMO)

Re MC Blog post - intresting so 66.102.7.104. is becoming Jagger1 - (what was it before?)

>> Stephen, I don’t think we support crawl-delay in robots.txt.

I know - lol ;)

This 1222 message thread spans 123 pages: 1222