so tomorow morning, Friday we hope to see some final stabilization?
Atomic
1:20 am on Nov 4, 2005 (gmt 0)
so tomorow morning, Friday we hope to see some final stabilization?
If there was a list of things we won't see Friday, I would start it with SERP stabilization.
spaceylacie
1:22 am on Nov 4, 2005 (gmt 0)
I like what I'm seeing so far with Jagger Part 2. This weekend will complete the third part of the trilogy... then back to work on Monday, working upon what we've learned. I think G's new algos are headed in the right direction.
macdave
1:35 am on Nov 4, 2005 (gmt 0)
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.
It's definitely high for a single bot, although it really shouldn't be enough to overwhelm a modern server. Of course, a database-intensive site may reach saturation sooner than static HTML. And if you're on shared hosting, consider that the bot may be simultaniously hitting a couple hundred other sites on the same server.
Yippee
1:40 am on Nov 4, 2005 (gmt 0)
Yeah, see if your host is using e-Machines. Also, you might consider looking into how often you are hitting the DB per page request. We are averaging about 2 DB hits per page request and we seem to be holding up fine. However, our site is running on a 8 server farm.
rmccollom
2:10 am on Nov 4, 2005 (gmt 0)
Do any of you guys actually work...at all?
Geez.
walkman
2:14 am on Nov 4, 2005 (gmt 0)
>> Do any of you guys actually work...at all? what are you talking about? Datacenter Watcher is the fastest rising segment in jobs these days ;)
aliszka
2:18 am on Nov 4, 2005 (gmt 0)
>>Do any of you guys actually work...at all?<<
we all like talking about broken search engines!
aliszka
2:20 am on Nov 4, 2005 (gmt 0)
I must admit these results are getting a little better: 66.102.7.104
pteam
2:32 am on Nov 4, 2005 (gmt 0)
66.102.7.104 now looks like pre-jagger results *slightly* modified with 10% jaggerness :)
