Skip to content
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

Crash OutOfMemory send push all. 3m user. #2552

Closed
nangdv-info opened this issue Aug 19, 2016 · 21 comments
Closed

Crash OutOfMemory send push all. 3m user. #2552

nangdv-info opened this issue Aug 19, 2016 · 21 comments

Comments

@nangdv-info
Copy link

I have problems sending push all user. It is report OutOfMemory. I sended 3M user. Please help me.

@benishak
Copy link
Contributor

benishak commented Aug 19, 2016

check this PR #2444
you can subscribe your users to sns topic and send the push to the topic, then aws will send the push to all user subscribed in the topic.

you can use my forked sns-adapter which supports sending to topic
https://github.com/benishak/parse-server-sns-adapter
#2444 (comment)

@nangdv-info
Copy link
Author

Thanks for answering. I need one other solution. Thanks. I think you can fix the code to send one little parseserver.

@benishak
Copy link
Contributor

Use AWS SDK to subscribe users to SNS topic. Won't work out of the box ...

@nangdv-info
Copy link
Author

If using SNS . i think .I pay 3$/notify and maybe more.

@benishak
Copy link
Contributor

SNS is 50 cent per 1Mio notification! First 1 Mio is free. In your case you pay $1 for your first 3M pushes

@nangdv-info
Copy link
Author

I just want to use to push parseserver. I successfully sent a few users. I installed ubuntu EC2 and Amazon (16G Ram, 4CPU). how users maximum send in parseserver. What solution to i only parseserver? Thanks You.

@flovilmart
Copy link
Contributor

We lack a good system to batch large sends like the one you describe. So no matter how big the AWS instance you run, it's unlikely to perform well.

@nangdv-info
Copy link
Author

Thanks u for answer. what is solution to the problem ?. I should choose solutions . Thanks U.

@otymartin
Copy link

otymartin commented Aug 22, 2016

@parseserverpush Perhaps onesignal.com

@nangdv-info
Copy link
Author

@otymartin : How much it it. Thank u.

@benishak
Copy link
Contributor

OneSignal is free

@khirr
Copy link

khirr commented Aug 29, 2016

Hi, I had a similar problem, when I have to send too much notification I divide in 1k instalations part every 5 seconds, you can create your own clode code for this prupose and works softly, database server load increase 0.5% only.

@nangdv-info
Copy link
Author

@khirr You can share it. Thanks You.

@khirr
Copy link

khirr commented Aug 30, 2016

Hi, for now I can't because is a part of a bigger system but I can explain how does it works.

@nangdv-info
Copy link
Author

I understand. You can send me acc Skype ?. Thanks

@khirr
Copy link

khirr commented Aug 30, 2016

Yes but, I prefer explain you here, maybe somebody else needs it in the future.

The short answer is using CURL for this:
http://blog.parse.com/announcements/parse-server-push-notifications/

As you can see, you can use filters to send, so you can you Skip, Limit, all filters that you need.

You can do it using PHP and Parse PHP SDK, I use it.

I hope this can help you.

@nangdv-info
Copy link
Author

Yes. I also think this resolution. But it can send the order and maximum pushnotify user? Thanks You.

@nangdv-info
Copy link
Author

Hi @khirr
Can I use "limit" and "skip" on post pushNotify ?.
Thanks You very much.

@khirr
Copy link

khirr commented Aug 31, 2016

For example, you can get installation ids using a function in PHP SDK, get 1k per time, and send it in where clause, _id: $in[] or installationsId: $in[], you can check it con REST guide:

http://parseplatform.github.io/docs/rest/guide/#push-notification

@nangdv-info
Copy link
Author

I have sent a lists of _id. It's very long.

@flovilmart
Copy link
Contributor

Thanks for your question!

We want to make sure to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track issues that affect the development of Parse Server.

Questions like yours deserve a purpose-built Q&A forum. Would you like to post this question to Stack Overflow with the tag #parse.com? We'll be happy to answer there. Post a link to your Stack Overflow question here, so that we don't lose track of it.

You may also use Server Fault for questions about managing your own servers.

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

5 participants