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

Memory profiling #284

Open
yaymukund opened this issue Oct 12, 2021 · 0 comments
Open

Memory profiling #284

yaymukund opened this issue Oct 12, 2021 · 0 comments

Comments

@yaymukund
Copy link
Contributor

I'm noticing [...] that the chain watcher of the customer is a little CPU heavy, or at least has a quite constant CPU load. Also, both the customer watcher and the Merchant seem to have somewhat of a memory leak, not necessarily much, but it might grow over time... I noticed the memory usage increases a bit over time. Maybe it's necessary information, but I would think that memory should stay quite stable over time given that most of the data is stored in the db anyway (and not in memory)

We can profile the memory, maybe with something like https://github.com/koute/bytehound

This was in debug mode, so we should also compare with --release performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant