Does anyone know device quota per day for Android c2dm?
PS: Im not interesting in application quota that is 200 000.
C2DM quotas is indeed based both on number of messages to a device or messages sent for any device.
It doesn't however seem to be stated anywhere what the amounts for a single device is.
When you sign up you give an estimate of how many messages you expect your application to send. (And are assigned a default quota of 200,000)
You can read about the limitations of c2dm here
And you can read about the quotas here. Here you will also be able to request more than the default 200,000 messages.
Device quota is 1000 per application per device. Here is answer on Google groups
Related
We're building an application server which will be used to send push notifications to android and ios clients via GCM connection server. Our plan is to use HTTP interface to connect with GCM as we only want downstream messaging. could you please tell me what is the performance of GCM for HTTP interface? I'm looking for some kind of performance data like how many push notifications messages per second GCM can support? I checked GCM site but couldn't find this. Please help to guide from where i can get such data?
as per the official Google answer
The rate limit exception code indicates that you are sending messages from a backend server too frequently. To ensure a stable service, there is a per minute / per device app upper limit on the number of messages that can be sent from a backend server. This limit is set high so most well behaving apps should not be affected, all apps should however be prepared to receive this error code.
They do not specify the "actual limit" but they do say This limit is set high so most well behaving apps should not be affected so as long as you re not spamming a single device like crazy you should be ok with whatever you send at it.
However please note that you can get throttled and have the messages be delayed
StackOverflow, i need your help! I've read gcm documentation here http://developer.android.com/google/gcm/adv.html and don't understand fully what means "GCM only allows a maximum of 4 different collapse keys to be used by the GCM server per device at any given time". I want to explain for myself it. I can assume that if on my phone N applications are installed (facebook, twitter, instagramm, myMail, facebook and other), there is no guarantee that when my device for example will return to online, GCM will choose collapse_key of my app. Am i right or no?? If I am right in what sense of this collapse key if there is no guarantee that it will work and that my app will receive at the right time the necessary notification? I need to point that pattern "Sync-to-load" is very preferrable for me and i want to use it, but I am afraid that problems will begin when user will be write in comments "My device come back online, but i missed all messages:(("
The limit on GCM collapse_keys is on a per app level and is not affected by what other apps the user has installed on their phone.
Does anyone know for how long Google will try to deliver a C2DM message before it gives up (even approximately)? 1 week? 2 weeks? 1 day? Of course assume registration is correct and everything but say, the device is offline.
Of course I've already searched to questions like this but there is no answer to my particular question.
I understand I should have a check myself with an ack of some sort, but I still would like to know when google gives up on delivery.
Thanks.
The time Google tries to deliver C2DM messages is approx. 28 days.
I planning the application pushes a newsletter to all registered users.
Number of users is approximately 200,000 ~ 300,000.
I'm caring about the traffic issue with google c2dm server.
Can I request to c2dm server in a loop with large number of users using HttpURLConnection?
Will I banned?
I heard something about in this case I must use http 1.1 protocol with keepAlive set true.
C2DM does have quotas, both on the messages per device and total number of messages. you can find the details here:
http://code.google.com/android/c2dm/quotas.html
as it says, 200k is the default limit but you can request a larger quota. i've done this at a company and it was no problem, but i can't say for sure how helpful they will be to the average developer.
as far as i know, there's no quota on the rate that you send them. you can send them as fast as the google servers will accept your requests.
I planning the application pushes a newsletter to all registered
users.
you should make sure you aren't trying to push a payload through C2DM. that's clearly a misuse of the service. C2DM must be used to wake up the device only. in your case, the message itself should be "hey device there's a new newsletter on the server, go get it". assuming that's happening but a few times a day at most, it will be within the accepted use for C2DM.
As of 5/2011 the google documentation for c2dm says this:
"Google limits the number of messages a sender sends in aggregate, and the number of messages a sender sends to a specific device"
What is the specific limitation? If my server sends 10 messages a day to 10,000 devices will Google shut my app down?
When you signup C2DM here, you're asked to fill in a estimated "Estimated total number of messages per day" and "Estimated peak queries per second (QPS)".
According the C2DM quotas page, the currently default limit is approximately 200,000 messages per day.
If your requirement exceeds this limit, you should make sure using C2DM correctly, and submit the request quotas at the bottom link of the quotas page.
The specific limitation is derived per account and is modifiable upon (reasonable) request. For example, I have c2dm account which is "restricted" to "just" 100,000 c2dm messages per day.
If you worry about message count limitation, you should switch to GCM anyways.
There is only a limit of messages saved before collapsing, which is 100.
C2DM is deprecated and has been replaced by Google Cloud Messaging for Android (GCM).
Google's statement:
Important: C2DM has been officially deprecated as of June 26, 2012.
This means that C2DM has stopped accepting new users and quota requests.
No new features will be added to C2DM. However, apps using C2DM will continue to work.
Existing C2DM developers are encouraged to migrate to the new version of C2DM,
called Google Cloud Messaging for Android (GCM).
See the C2DM-to-GCM Migration document for more information.
Developers must use GCM for new development.
There is a demo app tutorial for GCM and also for migration from C2DM.