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

Add timeout to web push workers and stop retries when getting 4xx #9434

Merged
merged 1 commit into from
Dec 17, 2018

Conversation

Gargron
Copy link
Member

@Gargron Gargron commented Dec 5, 2018

No description provided.

@Gargron Gargron added the performance Runtime performance label Dec 5, 2018
@ClearlyClaire
Copy link
Contributor

1-3s is a bit on the low end, no? Why not something closer to the timeouts we use for basically everything else?

@Gargron
Copy link
Member Author

Gargron commented Dec 5, 2018

Because webpush endpoints are either Mozilla or Google or Apple, or an app developer, i.e. I can expect it to not be under heavy load or to be able to handle big loads. 1 second for a request is really long! It's also not that critical.

@ClearlyClaire
Copy link
Contributor

Hm, the instance issuing the notifications may itself have connectivity issues/be under load.

Are those tasks really causing delays? If so, those changes are probably stopping legitimate notifications from being delivered, right?

@Gargron Gargron merged commit 628da11 into master Dec 17, 2018
@Gargron Gargron deleted the fix-web-push-retry branch December 17, 2018 02:14
abcang pushed a commit to pixiv/mastodon that referenced this pull request Oct 1, 2019
hiyuki2578 pushed a commit to ProjectMyosotis/mastodon that referenced this pull request Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance Runtime performance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants