Skip to content

Implement dsize function for fstring_table_type #13138

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

Merged
merged 1 commit into from
Apr 19, 2025

Conversation

byroot
Copy link
Member

@byroot byroot commented Apr 19, 2025

The fstring table size used to be reported as part of the VM size, but since it was refactored to be lock-less it was no longer reported.

Since it's now wrapped by a T_DATA, we can implement its dsize function and get a valuable insight into the size of the table.

{"address":"0x100ebff18", "type":"DATA", "shape_id":0, "slot_size":80,
"struct":"VM/fstring_table", "memsize":131176, ...

FYI: @jhawthorn

The fstring table size used to be reported as part of the VM
size, but since it was refactored to be lock-less it was no
longer reported.

Since it's now wrapped by a `T_DATA`, we can implement its
`dsize` function and get a valuable insight into the size
of the table.

```
{"address":"0x100ebff18", "type":"DATA", "shape_id":0, "slot_size":80,
"struct":"VM/fstring_table", "memsize":131176, ...
```
@byroot byroot enabled auto-merge (rebase) April 19, 2025 03:03
@byroot byroot merged commit 0f25886 into ruby:master Apr 19, 2025
84 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant