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

Add "Total Machine Code Cost" of UOps to PyStats #119692

Open
JeffersGlass opened this issue May 28, 2024 · 0 comments · May be fixed by #119693
Open

Add "Total Machine Code Cost" of UOps to PyStats #119692

JeffersGlass opened this issue May 28, 2024 · 0 comments · May be fixed by #119693

Comments

@JeffersGlass
Copy link
Contributor

JeffersGlass commented May 28, 2024

At the sprints at PyConUS 2024, @brandtbucher suggested an improvement to pystats data. Right now, the Tier 2 stats include a count of how many times each UOp is executed, but Brandt suggested another useful table would be UOp Execution Count * Length of UOp in Machine Instructions, sorted by this metric.

In this way, UOps that are extremely common but cheap can be deprioritized, and work can be focused on improving UOps that are less common but take up more 'time' overall (with machine code length as a proxy for time).

I'm happy to take this on.

Linked PRs

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 a pull request may close this issue.

1 participant