-
Notifications
You must be signed in to change notification settings - Fork 379
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
box.tuple.new: hidden memory usage #5872
Comments
kyukhin
added
srv.info
Collection of maintenance tickets about box.info like interfaces
teamC
and removed
incoming
labels
Jul 29, 2021
This hurts from time to time, I disagree with "wishlisting" |
Totktonada
added a commit
to Totktonada/tarantool
that referenced
this issue
Apr 13, 2022
See the documentation request below for details. Fixes tarantool#5872 @TarantoolBot document Title: New `box.info.memory().runtime` metric It allows to track memory allocated for tuples on runtime arena. It does not count tuples owned by memtx and vinyl, but tracks so called runtime tuples. The most common example is a tuple created by the `box.tuple.new(<...>)` function. Example: ```lua tarantool> box.info.memory().runtime -- 0 tarantool> box.tuple.new({}) tarantool> box.info.memory().runtime -- 160 tarantool> box.tuple.new({}) tarantool> box.info.memory().runtime -- 320 tarantool> collectgarbage() tarantool> box.info.memory().runtime -- 160 ```
Totktonada
added a commit
to Totktonada/tarantool
that referenced
this issue
Apr 13, 2022
See the documentation request below for details. Fixes tarantool#5872 @TarantoolBot document Title: New `box.info.memory().runtime.tuple` metric It allows to track memory allocated for tuples on runtime arena. It does not count tuples owned by memtx and vinyl, but tracks so called runtime tuples. The most common example is a tuple created by the `box.tuple.new(<...>)` function. Example: ```lua tarantool> box.info.memory().runtime.tuple -- 0 tarantool> box.tuple.new({}) tarantool> box.info.memory().runtime.tuple -- 160 tarantool> box.tuple.new({}) tarantool> box.info.memory().runtime.tuple -- 320 tarantool> collectgarbage() tarantool> box.info.memory().runtime.tuple -- 160 ```
Totktonada
added a commit
to Totktonada/tarantool
that referenced
this issue
Apr 14, 2022
See the documentation request below for details. Fixes tarantool#5872 @TarantoolBot document Title: New `box.info.memory().runtime.tuple` metric It allows to track memory allocated for tuples on runtime arena. It does not count tuples owned by memtx and vinyl, but tracks so called runtime tuples. The most common example is a tuple created by the `box.tuple.new(<...>)` function. Example: ```lua tarantool> box.info.memory().runtime.tuple -- 0 tarantool> box.tuple.new({}) tarantool> box.info.memory().runtime.tuple -- 160 tarantool> box.tuple.new({}) tarantool> box.info.memory().runtime.tuple -- 320 tarantool> collectgarbage() tarantool> box.info.memory().runtime.tuple -- 160 ```
Totktonada
added a commit
to Totktonada/tarantool
that referenced
this issue
Apr 14, 2022
See the documentation request below for details. Fixes tarantool#5872 @TarantoolBot document Title: New `box.runtime.info().tuple` metric It allows to track memory allocated for tuples on runtime arena. It does not count tuples owned by memtx and vinyl, but tracks so called runtime tuples. The most common example is a tuple created by the `box.tuple.new(<...>)` function. Example: ```lua tarantool> box.runtime.info().tuple -- 0 tarantool> box.tuple.new({}) tarantool> box.runtime.info().tuple -- 160 tarantool> box.tuple.new({}) tarantool> box.runtime.info().tuple -- 320 tarantool> collectgarbage() tarantool> box.runtime.info().tuple -- 160 ```
locker
pushed a commit
that referenced
this issue
Apr 15, 2022
See the documentation request below for details. Fixes #5872 @TarantoolBot document Title: New `box.runtime.info().tuple` metric It allows to track memory allocated for tuples on runtime arena. It does not count tuples owned by memtx and vinyl, but tracks so called runtime tuples. The most common example is a tuple created by the `box.tuple.new(<...>)` function. Example: ```lua tarantool> box.runtime.info().tuple -- 0 tarantool> box.tuple.new({}) tarantool> box.runtime.info().tuple -- 160 tarantool> box.tuple.new({}) tarantool> box.runtime.info().tuple -- 320 tarantool> collectgarbage() tarantool> box.runtime.info().tuple -- 160 ```
Documentation issue: tarantool/doc#2829. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
In case when using
box.tuple.new
there is no place to understand how many memory is used.Initial state:
pmap
"hidden" allocation
after state
the only pmap can show us the memory metrics
Consider to expose box.tuple pool memory metric
https://gist.github.com/Totktonada/08219ca0cc014a66b83dee6539b80348
The text was updated successfully, but these errors were encountered: