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

consider using sync.Pool for heavy allocations #1866

Open
nkryuchkov opened this issue Nov 21, 2024 · 0 comments
Open

consider using sync.Pool for heavy allocations #1866

nkryuchkov opened this issue Nov 21, 2024 · 0 comments
Labels
enhancement New feature or request optimization Something to make SSV run more efficiently

Comments

@nkryuchkov
Copy link
Contributor

nkryuchkov commented Nov 21, 2024

Is your feature request related to a problem? Please describe.
Some parts of code like message validation or non-committee observer allocate a lot of memory

Describe the solution you'd like
Analyze if we could use sync.Pool to reuse the same memory and reduce the amount of allocations. Implement it if so.

Additional context
Use Pyroscope to find where we need to apply it first

@nkryuchkov nkryuchkov added enhancement New feature or request optimization Something to make SSV run more efficiently labels Nov 21, 2024
@nkryuchkov nkryuchkov changed the title use sync.Pool for heavy allocations consider using sync.Pool for heavy allocations Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request optimization Something to make SSV run more efficiently
Projects
None yet
Development

No branches or pull requests

1 participant