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

gh-128842: collect JIT memory stats via pystats #128941

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

diegorusso
Copy link
Contributor

@diegorusso diegorusso commented Jan 17, 2025

Collect via pystats the following metrics:

  • total memory size
  • code size
  • trampoline size
  • data size
  • padding seze
  • freed memory size

Also print and histogram of the traces total size.

@diegorusso
Copy link
Contributor Author

I deleted the branch by error. It's now restored.

diegorusso and others added 2 commits January 23, 2025 08:39
Collect via pystats the following metrics:
* total memory size
* code size
* trampoline size
* data size
* padding seze
* freed memory size
@diegorusso diegorusso added topic-JIT type-feature A feature request or enhancement performance Performance or resource usage and removed type-feature A feature request or enhancement performance Performance or resource usage labels Jan 23, 2025
@diegorusso
Copy link
Contributor Author

This is what the output looks like: https://gist.github.com/diegorusso/51df19523da041035ec819dac18ae958

Copy link
Member

@brandtbucher brandtbucher left a comment

Choose a reason for hiding this comment

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

Thanks for tackling this! The JIT changes look good to me. Really like the histogram, that's super useful information.

@mdboom, looping you in to review the stats changes.

Two very minor requests, if they're easy to do (fine if it's not worth the effort):

  • Can capitalize "jit" in the output stats? It looks kind of weird when lowercased like that.
  • Can we automatically detect and drop histogram buckets at the low end of the range with 0 values, and start the histogram with the first nonzero value?

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

Successfully merging this pull request may close these issues.

3 participants