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

Push notification taking too long to arrive #184

Open
Chileads opened this issue May 5, 2022 · 1 comment
Open

Push notification taking too long to arrive #184

Chileads opened this issue May 5, 2022 · 1 comment

Comments

@Chileads
Copy link

Chileads commented May 5, 2022

Push notification can take up to 10hrs to arrive especially for incoming transactions. I mainly use the notification to know when their is incoming transactions because the transaction does not appear even when you open and refresh the app. When I get a notification I go to "coin control" to verify the amount.

I learnt that it's cause of traffic in the groundcontrol-bluewallet.herokuapp.com server that's causing the delay in notification.
I suggest we should have multiple servers or alternatives for app notifications.

@Overtorment
Copy link
Member

Overtorment commented May 10, 2022

yes, the problem is the sender is a single process and is not refactored to run in multi-process.
sometimes send queue grows to tens of thousands and it takes hours to clear.

when the queue is not clogged notifications should be instant.

for some reason people add exchange's hot wallets as a watch only and receive all their their txs as pushes. some addresses have 300k+ transactions.

i did some work recently to ignore "thick" addresses to not slow things down for everyone else

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

2 participants