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.

Sign up for GitHub

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

Jump to bottom

Introduce profiling to find bottlenecks #225

Open

maschad opened this issue Feb 12, 2025 · 1 comment

Member

maschad commented Feb 12, 2025

We should have some sort of profiling in place to find potential bottlenecks particularly around message processing.

We could explore integrating flamegraph and/or pprof

Originally posted by @maschad in #105 (comment)

Contributor

jorgeantonio21 commented Feb 12, 2025

Love the initiative, this is much needed moving forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment