I'm confused with Firebase's quota limit. Is the 20k writes per day consumable per user or for all users?
It's per project irrespective of how many users you have.
Related
We have a resource of our client with more than 10 000 000 sessions (not hits) per month. Is it possible that they will contact our client soon and ask him to use a paid account in Universal Analytics (or to reduce the data volume)?
I've had this conversation a while ago and yes, if your clients exceeds the hit quota on an ongoing basis Google reserves the right to contact him an make him either buy the commercial version of Google Analytics, reduce the processing volume by implementing a sample rate limit (which would mean you client does not track all their visitors) or, after a period of non-compliance, terminate the account. FWIW, they assured us that they would never shut down an account without prior notice as long as messages to the e-mail-adresses in the account in question elicit a response.
We are getting the below issue when querying facebook graph API
(#17) User request limit reached
i know that this is a throttling error on user level rate limiting as mentioned in the below link
https://developers.facebook.com/docs/marketing-api/api-rate-limiting
But we were never facing the issue before, suddenly this issue has started coming, Did facebook changed the rate limits recently ?
does anybody have any idea ?
AS Per doc:
Your app can make 200 calls per hour per user in aggregate. As an example, if your app has 100 users, this means that your app can make 20,000 calls. This isn't a per-user limit, so one user could make 19,000 of those calls and another could make 1,000. This limit is calculated based on the number of calls made in the previous hour.
The number of users for your app is calculated as the average number of daily active users plus today's new logins
Not all API calls are subject to rate limits so the number of calls you make may not match what you see in the rate limit tool. Facebook also throttles calls based on CPU time used and total time. It is difficult to hit these limits, so it is an extremely rare occurrence. This information is exposed in the detail pane for each sample. Click on the graph in the rate limit tool on your dashboard for details.
Recommendations:
Rate limiting defines limits on how many API calls can be made within a specified time period. When a rate limit is exceeded, all API calls from an app are throttled and fail for a brief period of time. Once an app is throttled, the caller will get an error for subsequent calls with error code = 4, CodedException. It can take up to an hour for your requests to be accepted again.
To avoid rate limiting:
Spread out queries evenly between two time intervals to avoid sending traffic in spikes. Use filters to limit the data response size and avoiding calls that request overlapping data. Use the rate limiting header to dynamically balance your call volume.
You called API too many times (working too hard, huh?). This is how Facebook calculates the Limit. ref: link
I know that fb have made available some documentation about the requests limits to the api https://developers.facebook.com/docs/marketing-api/api-rate-limiting,
but it is not clear how each api call is calculated...
i.e, If I want to get stats for ~10,000 adsets, how can I evenly space the time between the calls ?
The best answer i could find for this question from another SO thread -
"After some testing and discussion with the Facebook platform team, there is no official limit I'm aware of or can find in the documentation. However, I've found 600 calls per 600 seconds, per token & per IP to be about where they stop you. I've also seen some application based rate limiting but don't have any numbers.
As a general rule, one call per second should not get rate limited. On the surface this seems very restrictive but remember you can batch certain calls and use the subscription API to get changes."
Source - What's the Facebook's Graph API call limit?
Official Doc-: https://developers.facebook.com/docs/graph-api/advanced/rate-limiting
Rate limits are imposed on each app. The rate limiting tool gives you information about how close your app is to being throttled. Click on any sample to get more detail on the types of utilization.
Your app can make 200 calls per hour per user in aggregate. As an example, if your app has 100 users, this means that your app can make 20,000 calls. This isn't a per-user limit, so one user could make 19,000 of those calls and another could make 1,000. This limit is calculated based on the number of calls made in the previous hour.
Source-: https://developers.facebook.com/docs/graph-api/advanced/rate-limiting
Heavily rate-limited per ad account. For development only. Not for production apps running for live advertisers.
If the answer is yes, then what is it?
By maximum number of connectioned allowed per application I mean how many instances of the same api/key can be used to get the friends list at any one time, will Facebook block too many requests?
EDIT I have been looking at http://developers.facebook.com/ but have not been able to find the answer to my question there.
From their Policy
If you exceed, or plan to exceed, any of the following thresholds please contact us as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day).
The only information I was able to find is something in a forum.
http://www.quora.com/Whats-the-Facebook-Open-Graph-API-rate-limit
After some testing and discussion with the Facebook platform team,
there is no official limit I'm aware of or can find in the
documentation. However, I've found 600 calls per 600 seconds, per
token & per IP to be about where they stop you. I've also seen some
application based rate limiting but don't have any numbers.
As a general rule, one call per second should not get rate limited. On
the surface this seems very restrictive but remember you can batch
certain calls and use the subscription API to get changes.
You can see how many API requests your users can have a day if you go to your Insights page and click on "Diagnostics". You can also see some other request statistics if you click on "Performance".
http://www.facebook.com/insights
I need your expert advice on this one.
I have been asked to analyse a potential Facebook application.
This application is a parental monitoring for kids accounts. Basically it will search a kid status message for specific keywords amongst others things. And this application will alert the parents when it finds something.
Of course this application will have a valid token to access the kid's data. This is not a tool to spy on the kid.
I am using the Graph API coupled with the 'since' keyword to get the last updates. It's working fine with a single user.
My question is about scalability.
How should I get updates of a huge number of kids to monitor? (between 10,000 and 100,000 accounts)
And for each kids I have to monitor status messages, videos, images, friend, friends' status messages...
Here are some numbers:
~2.1M requests each day to get hourly updates of 10,000 kids' account.
~57.8M requests each day to get hourly updates of 10,000 kids'account plus their friends', with an average of 40 friends each.
And as I read here, it would be limited.
So what do you reckon?
ps: Maybe with real-time updates I won't have this problem or would it be worse?
Yes I would subscribe to real-time updates so as an account gets updated you get a callback and then you get the latest updates. This would avoid the overhead of constantly polling accounts for updates. You will need to get an offline_access token for this to work as well.