Skip to content

[Experimental] Measure the space used by vtable pointers #7487

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

Open
wants to merge 1 commit into
base: heap-snapshot-analysis
Choose a base branch
from

Conversation

tlively
Copy link
Member

@tlively tlively commented Apr 11, 2025

This is the space that could be saved by using custom descriptors.

This is the space that could be saved by using custom descriptors.
@tlively tlively requested a review from kripken April 11, 2025 01:43

// Measure the savings of removing vtable pointers. Assume any object that
// contains an edge to another object that contains an edge to a "system /
// WasmFuncRef" contains a vtable pointer.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How precise do you think this is?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be fairly precise. I don't know of any other patterns involving function references, do you? I have samples with name sections so I can do another analysis where I just look for "vtable" in the type name and compare the results to make sure.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't say I know of one, but I remember talk about caching function pointers in some cases... Good idea to compare to types with "vtable" in the name, yeah, that would give a lot more confidence.

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

Successfully merging this pull request may close these issues.

2 participants