Skip to content

Parse Push Documentation Questions #2251

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
StuartMorris0 opened this issue Jul 11, 2016 · 11 comments
Closed

Parse Push Documentation Questions #2251

StuartMorris0 opened this issue Jul 11, 2016 · 11 comments

Comments

@StuartMorris0
Copy link

Hello,

I am reviewing the wiki page for parse push and have a couple of questions:
https://github.com/ParsePlatform/Parse-Server/wiki/Push

However, there are a few caveats:
Does not support super high throughput since it does not employ a job queue system

Please confirm what this means in a more detail? What amount of pushes could be sent until it is considered super high throughput?

Further to this, within the API section of the document:

Here is the list of sending options we do not support yet:
...
Increment badge under data for iOS badge number

Does this mean a push notification send to an iOS device from CloudCode(Parse Server) would not increment the badge number on the client device?

Thank you.

@sprabs
Copy link

sprabs commented Jul 12, 2016

increment should work fine. I think that information hasn't been updated in a while.

@StuartMorris0
Copy link
Author

@sprabs Thanks, so what about the super high throughput?

@flovilmart
Copy link
Contributor

The amount depends on your server hardware configuration. Think of it as a loop that goes through all the found devices and then try to deliver the push.

@StuartMorris0
Copy link
Author

@flovilmart Thanks. I was reading it as it does not queue when sending a bunch of different pushes, but from what you are saying the issues are when sending from 1:many.

So just to be clear, we are looking for lets say 50,000 different users sending a push to one user each potentially within the same time block of 10 minutes. Would there be an issue there or would you recommend using a third party like One Signal and using their parse push adapter?

@flovilmart
Copy link
Contributor

the bottleneck is on the installations query. So no matter what adapter you use, that may be problematic. if your query only returns 1 installation you should be fine IMHO. The best way to know is to closely monitor the logs and give it a go

@StuartMorris0
Copy link
Author

@flovilmart Thanks that makes perfect sense. Is the issue with the installation query just the time it takes to return?

Furthermore what is actually meant by this statement "Does not support super high throughput since it does not employ a job queue system"

@flovilmart
Copy link
Contributor

Complexity in time and space. Each push is delivered to APNS at once, consecutively, the more installations thé longer it takes

@StuartMorris0
Copy link
Author

@flovilmart

@StuartMorris0
Copy link
Author

@flovilmart Unless you want this open to update the wiki...

@StuartMorris0 StuartMorris0 reopened this Jul 12, 2016
@sprabs
Copy link

sprabs commented Jul 16, 2016

@StuartMorris0 Since we are on the topic, are you seeing issues with push notifications on Parse Server (in terms of compatibility with clients on parse.com)?

I created this issue here that should affect everyone migrating: #2275

@flovilmart
Copy link
Contributor

@StuartMorris0 I'll be closing that one, as we have other issues open for improving the push notification batching, scheduling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants