If any one knows Uber API best practises, then please let me know. Google Driving and Transit API takes less than 100 milliseconds and Uber API takes more than 1 sec.
Thanks in advance.
I do not have any specific recommendations to reduce the time. That amount is higher than we are seeing for most hits to /v1.2/estimates/price over the last 7 days but is at the upper range for all requests to that endpoint.
The Uber API team will continue working on optimizing and improving speed for the Uber API. Thanks.
Related
We use the REST API to check the last 20 transactions for a specific user
What is the max number of requests per seconds we can make using the Elrond REST API ?
The rate limits for the official api aren't known as far as I'm aware.
If you plan to have a lot of requests each second you might want to consider setting up your own observer squad and api so you can be independent from the elrond infrastructure. This not only gives you greater control over the response times (and downtimes), but you will also reduce the load on the official servers so others won't be affected by the amount of requests you make.
I am developing an app in Flutter and ReactNative to display realtime weather for a list of cities. I am retrieving the weather data from OpenWeatherMap. I am finding it hard to understand the concept of calls per minute. There is a limit of 60 calls/minute on a free plan, 600 for Startup plan, and so on.
My question is, if by some miracle my app has 100,000 users in the future, and they all have 5 cities in their app, does this mean that to get realtime weather data the number of API calls would be 5x100,000 at any given moment for my single registered API key?
Even with an enterprise plan (200,000 calls/minute), this seems not achievable.
Am I missing something here? I am interested in realtime data, not historical. The analogy could be extended to a stock trading app as well where I would loop fetchData() over an interval of 1 or 2 seconds. But if there are thousands of users, I'm not sure how to handle the calls.
Please help me understand how I can achieve this or if I'm wrong somewhere.
Does anyone know what the rate limit is for Adwords API keyword Targeting Ideas service?
It seems they mention some rate limits but it doesn't seem to have any details around queries per second
I've not been able to get an official answer on this but support have told me that the rate limit on the targeting ideas service varies by how busy this service is. My experience confirms this.
Also: the recommended backoff of 30 seconds returned in the rate limit error message is almost never enough. I've ended up defaulting to a 2 min backoff for this service.
I understand the Twitter REST API has strict request limits (few hundred times per 15 minutes), and that the streaming API is sometimes better for retrieving live data.
My question is, what exactly are the streaming API limits? Twitter references a percentage on their docs, but not a specific amount. Any insight is greatly appreciated.
What I'm trying to do:
Simple page for me to view the latest tweet (& date / time it was posted) from ~1000 twitter users. It seems I would rapidly hit the limit using the REST API, so would the streaming API be required for this application?
You should be fine using the Streaming API, unless those ~1000 users combined are tweeting more than (very) roughly 60 tweets per second at any moment.
Using the Streaming API endpoint statuses/filter with the follow parameter, you are allowed up to 5000 users. There is no rate limit except when the stream returns more than about 1% of the all tweets being tweeted at that moment. (60 tweets per second is 1% of the average rate of tweets, which is always fluctuating, so don't rely on that number.)
If your stream does go above the 1% threshold, you can detect this. (See the LIMIT notice.) Then you would use the REST API to find missed tweets.
Twitter simply will not allow multiple streams from one registered app/account. Doing so will result in the older one being closed.
Also too many connection tries are not allowed as well and will result in a user being blocked.
Reference docs: Public Streaming API (outdated)
Does anyone know what's the ratio between the number of tweets we get from twitter sample API over the total number of tweets which the Twitter server receives? I am doing some analysis based on the data read from the sample API, and would like to estimate the actual workload handled by Twitter server. I observed that the number of tweets we get from the API varies over time. So, I presume it is something like percentage sample. Any clue is highly appreciated.
Thanks
The sample stream /statuses/sample does return roughly 1% of all tweets. Twitter samples the tweets by delivering only tweets created within a 10-millisecond window out of the 1,000 milliseconds in every second. If you want more details, you can read my blog post: http://blog.falcondai.com/2013/06/666-and-how-twitter-samples-tweets-in.html
When Twitter Spritzer (basically the old-fashioned Streaming API) was launched, it was supposedly about 1-2% of all tweets. Based on my use of the current Streaming API, I'd be surprised if it was any more than 1% right now, and possibly less. According to the docs, the "Twitter streaming volume is not constant," but they neglect to mention if the volume outputted by the API is proportional to the rate of actual tweets.
On 2 February 2015 Twitter announced intent to reset the streaming API sample rate to 1% (it had crept higher unintentionally):
The public Streaming API sample endpoints (aka POST statuses/filter and GET statuses/sample) are intended to be levelled at approximately 1% of the public Tweet volumes at any time.
Due to some past inconsistencies in configuration, there have been periods of time where the volumes of Tweets delivered via the Streaming API may have exceeded these parameters.
This notice is to indicate that over the next couple of weeks, we will be making changes to the public Streaming API to rebalance the volume of Tweets at the 1% capacity that was intended.
This plot shows the effect of the reset on a typical tweet stream.
This is something I found at
https://brightplanet.com/2013/06/25/twitter-firehose-vs-twitter-api-whats-the-difference-and-why-should-you-care/. I hope you find this useful.
Studies have estimated that using Twitter’s Streaming API users can
expect to receive anywhere from 1% of the tweets to over 40% of tweets
in near real-time.
There are references to the studies they have cited at the bottom of the webpage.