Image
EAN-139780060224820   EAN-13 barcode 9780060224820
Product NameA Horse In Harry's Room (I Can Read Books)
LanguageEnglish
CategoryBook / Magazine / Publication
Short DescriptionHardcover
Amazon.comA Buy on Amazon ~ 0060224827
Price New5.00 US Dollars    (curriencies)
Price Used0.01 US Dollars    (curriencies)
Long DescriptionHarry keeps a horse in his room. A trusty horse only he can see. But then his parents take him to the country to see "real" horses. Horses that are free to run, kick, and nibble. Now Harry must decide: Does his horse need to be free, too?
Similar Items9780060224806: Grizzwold (An I Can Read Book)
9780060756352: Pip Squeak (I Can Read Book 1)
Created09-22-2012 3:10:39am
Modified08-04-2017 12:12:23pm
MD59f9a16ad8dc75ce5bfd80b43de3dfd33
SHA2563f68c37d0560fe4fc6440e98a800e1d13afb6a27e5ae1d01d13a97564aa58458
Search Googleby EAN or by Title
Query Time0.0092151

Article of interest

This is just a general comment to those that might be interested in some technical info about our site and how Google interacts with it.

Google is frigging amazing!

Their programmers are very curtious when it comes to their spiders and how they interact with various web sites. Apparently, they are sensative to the load that their spiders place on a web server and do a darn good job when it comes to not overloading a server.

Another major search engine is not quite so nice. If you don't tell them to leave you alone, they will hammer the heck out of your site and potentially bring you to your knees.

Over the past vew days, we have been doing a massive system backup to a couple new off-site backup servers. Normally, this process is pretty quick but because these were new servers they required fully syncronization. Well, I forgot to take into account the drain this could place on our server and I let more than one backup run at a time.

This caused our main server to experience a high load for several days. Google detected this load and backed off its crawling process which was very kind of them. The only bad thing is that when Google backed off, our monitoring process (mostly manual at this point) assumed everything was only slightly higher than normal.

Google may be awesome, but it can be frustrating some times too.

This cool and wonderful feature that Google has in place to prevent overloading a server had an unexpected side affect. Because Google thought our site was super busy (which it was) it reduced the number of people it was referring to the site too. DOH!

As we noticed the visitor count slowly drop we got very confused because the system load was still very high. And we noticed Google wasn't visiting as often as usual and then we saw it... The backup process had overloaded the system. Not to the extreme but enough to make Google think there was a problem. We still actually had plenty of bandwidth for real users just not as much for the bots that visit (which we limit when bandwidth is limited).

Anyway, it was a good learning experience and we are now seeing the referrals climb back up and the Google spider is picking up its pace again too.

We had to force a couple other bots (including that othe big search engine) to play nice because they were trying to take more than their share of our data.

All in all, Google is AWESOME and very powerful. So THANKS GOOGLE for playing nice with others!

Close

Search

Close

Share

Close

Dialog