I have been monitoring the relatively large number of these reports over the 
last several weeks, but I am finding it puzzling for a number of reasons. The 
biggest of these are:

First, I have been unable to reproduce the "QPS limit exceeded" error that has 
been reported. This includes on the pages linked from this and other threads 
regarding the matter. But also, it includes a couple of attempts I have made 
utilizing code on my local computer. For example, today, I took the very same 
code that webjockey used, eliminated anything not related to the Feeds API, and 
added additional feeds until I was requesting 100 individual feeds. I then 
refreshed the page 5 times in rapid succession, resulting in 500 individual 
requests. All of the requests returned as expected.

And second, I don't believe that the Feeds API will ever return an error that 
reads "QPS limit exceeded." Adam Feldman has supported this belief. If you 
trigger the throttling mechanisms on the Feeds API, the error message should 
read "Suspected terms abuse." or something to that effect.

A couple of tidbits that may be related to the issue, but not necessarily:

At least three of the sites reporting issues are using script(s) by Dynamic 
Drive. I have not taken time to really dissect their code, but there does not 
seem to be anything unusual. I am not convinced that this is an issue, but it 
is a commonality, especially considering at least one other site reporting an 
issue was not (at least when I checked) using Dynamic Drive scripts.

I investigated geographic dispersion of the sites, thinking it may be something 
with a particular data center. This may also explain why I am unable to 
reproduce the issue while others report that it persists. But there does not 
seem to be anything common there. Reports are from sites on at least 3 
continents in at least two languages. Although as a non-Googler, I certainly 
don't have access to their routing and load balancing systems to determine 
conclusively, I can only guess that there would be multiple data centers 
involved here.

Given that most or all of the sites reporting issues are running client-side 
applications, the issue can't be with the particular server(s) hosting the 
sites. The Feeds API creates a request directly to Google's servers, so once 
the original page is served, the originating server is not involved in any 
requests or responses from Google.

All of this adds up to this: we have ourselves a bit of a mystery. The problem 
is either isolated or intermittent, and without being able to reproduce and 
analyze it, it's almost impossible to diagnose, let alone fix. If you have any 
further insights into this issue, please post whatever you possibly can!

Jeremy R. Geerdes
Generally Cool Guy
Des Moines, IA

For more information or a project quote:
[email protected]

If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!

On Feb 25, 2012, at 2:00 PM, webjockey wrote:

> Been having trouble with the QPS limit being reached for a few weeks
> now. Feed API worked fine for at least two months prior to this. Have
> tried to 'throttle down' the number of items going in with no
> noticeable improvement. Here's a couple test pages from my site that
> automatically reload every five or ten minutes so you can see what I
> mean:
> 
> http://www.soonersetc.com/headline-news/
> http://www.soonersetc.com/headline-news/index2.html
> 
> Interestingly the page that is throttled down the least fails less
> often. Don't really understand how Google Code, Feed API, etc. work.
> All I know is what used to work great no longer does...
> 
> On Feb 24, 10:53 am, Carlos Eduardo Benincasa <[email protected]>
> wrote:
>> For some reason the Google Feed API is not working today.
>> 
>> As you can see in the code playground (http://code.google.com/apis/
>> ajax/playground/#load_feed), the API is not loading the RSS Feeds at
>> all.
>> 
>> It worked perfectly since this morning. What happened?
>> 
>> Regards,
>> Carlos
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Google AJAX APIs" group.
> To post to this group, send email to
> [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> To view this message on the web, visit
> http://groups.google.com/group/google-ajax-search-api?hl=en_US
> For more options, visit this group at
> http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Google AJAX APIs" group.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
To view this message on the web, visit
http://groups.google.com/group/google-ajax-search-api?hl=en_US
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en

Reply via email to