-
Notifications
You must be signed in to change notification settings - Fork 268
fix(fcm): Optimize SendEachInBatch
with worker pool
#695
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
3555f78
Refactor: Optimize SendEachInBatch with worker pool
google-labs-jules[bot] 62f245a
Refactor: Increase SendEachInBatch worker pool size to 50
google-labs-jules[bot] 4344b0e
Fix: Correct lint and build errors in messaging batch code
google-labs-jules[bot] 71c84b0
Fix: Add missing sync import to messaging_batch_test.go
google-labs-jules[bot] 9b3e83d
Fix: Correct multiple failures in messaging test suite
google-labs-jules[bot] b4cceca
Style: Ensure gofmt formatting for messaging batch code
google-labs-jules[bot] 5cb5c40
Style: Apply gofmt fixes including trailing whitespace
google-labs-jules[bot] d9f72ae
fix typo in variable name
lahirumaramba dd534ab
Merge branch 'dev' into fcm-sendeach-worker-pool
lahirumaramba File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would raising this to 100 to match the backend max concurrent stream limit be something we consider.
I think 50 is reasonable considering this multiplies per
sendEachInBatch
call.nit: Can we update the PR description to specify 50 workers per
sendEachInBatch
callThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point, I can run some tests with 100 workers to see if that affects performance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think 50 is a good place to start though. If there are multiple calls to this API, increasing it to 100 will demand a lot more local resources
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets go with 50 then!