Hi Kevin,

Just a few things to mention that may help.

First, the image call won't count towards the limit, only direct calls to api.themoviedb.org do.

Second, if you decide to not worry about hitting the limit for a second, do your test runtimes get faster with more tasks, or are they staying flat?

Third, you can also use the API stats page in your account and do some comparisons of how many calls are being registered just for a sanity check. Ie. if you're testing 50 movies, there should be 100 calls.

Cheers.

Hi Travis,

I forgot about the stats page, soon as i return from work ill give this a go and post back. As usual thanks for the quick response :)

Hi Travis,

So I stripped back my code and managed the Tasks more efficiently and can confirm that it running super quick.

I ran 100 tasks that made one simple request each(query movie name) that completed in 2.09 seconds, although this is fantastic it leads me to think that the 40 requests every 10 seconds is not working or disabled.

Can you confirm this is the case, I was expecting to see errors where I could manage this in my code.

Also, I can only see some very basic stats from my calls, are you able to drill down into a users requests to confirm that I exceeded the 40 calls?

Kevin

Hi Kevin,

I can confirm the limits are working but if you would like to see the status of your IP in the rate limiter you can inspect the headers of a request. An example:

Traviss-iMac:~ travisbell$ curl -vv "http://api.themoviedb.org/3/search/movie?api_key=###&query=the+martian"
*   Trying 75.101.138.13...
* Connected to api.themoviedb.org (75.101.138.13) port 80 (#0)
> GET /3/search/movie?api_key=###&query=the+martian HTTP/1.1
> Host: api.themoviedb.org
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Access-Control-Allow-Origin: *
< Cache-Control: public, max-age=21600
< Content-Type: application/json;charset=utf-8
< Date: Thu, 03 Dec 2015 15:13:11 GMT
< ETag: f812291e86e5d515984dc44cf9d41ac3
< Server: openresty
< Vary: Accept-Encoding
< X-RateLimit-Limit: 40
< X-RateLimit-Remaining: 39
< X-RateLimit-Reset: 1449155601
< Content-Length: 9548
< Connection: keep-alive

You can see the X-RateLimit-* headers report the current status of your IP.

Hi Travis,

Thank you, ill look into this and post back as soon as ive tested :)

Hi Travis,

Thank you for your help with this, I drilled down into the header and indeed seen the x-rate limit deducting each request.

all good now :)