Make rideshare golang-push memory configurable #2632
Merged
Conversation
This file contains 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
petethepig
approved these changes
Nov 2, 2023
bryanhuhta
added a commit
that referenced
this pull request
Nov 3, 2023
This reverts commit 7e9ef48.
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds some environment variables to help configure the "memory leak" in the Go rideshare example.
PARAMETERS_POOL_SIZEsets the max size of the pool (aka the max number of goroutines that will hang before a reset)PARAMETERS_POOL_BUFFER_SIZE_KBsets the amount of memory each goroutine will allocate in kb