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
track and expose lua memory usage #2958
Comments
Another thing: |
also count total number of interpreters |
make sure we can flush lua memory and we do not have any leaks from lua |
Re/ flush Lua memory:
Re/ leaks: |
so maybe it's not lua. it could be that we are still missing a rather large contributor to backing heap usage. |
or we have a memory leak |
I'll try to reproduce a case in which there's a gap between RSS and other means of accounting memory. If I succeed, I can investigate further. |
We integrate our own allocator into lua bindings (see
mimalloc_glue
) but we do not track its allocations.In some extreme cases it can be significant. Consider 20K-40K connections over k-threaded Dragonfly with
interpreter_per_thread=300
running bullmq read requests.End result: expose
used_memory_lua
(same name as in valkey) via /metrics and via "info memory".The text was updated successfully, but these errors were encountered: