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

Fix eval_lit performance bug #441

Closed

Conversation

Alex-Fischman
Copy link
Contributor

This PR fixes the performance bug in eval_lit as noticed by Yihong in 439.

@Alex-Fischman Alex-Fischman requested a review from a team as a code owner October 10, 2024 19:25
@Alex-Fischman
Copy link
Contributor Author

#439

@yihozhang
Copy link
Collaborator

yihozhang commented Oct 10, 2024

Nice! How does the flamegraph now look like for eggcc-extraction?

@Alex-Fischman
Copy link
Contributor Author

I think something's wrong with my flamegraphs, but I'm getting ~10s now compared to ~25s before.

main: before

this branch: after

@saulshanabrook
Copy link
Member

saulshanabrook commented Oct 12, 2024

We didn't get there in the meeting, but would there be interest in adding codspeed tracking? They support flamegraphs in CI and will also show the diff in the flamegraph between a PR and main, showing which parts improved and which parts were degraded. If there is, I am happy to add it.

@Alex-Fischman
Copy link
Contributor Author

I'm keeping this PR open to test with codspeed, but I will close it afterwards because it's subsumed by #442 .

Copy link

codspeed-hq bot commented Oct 16, 2024

CodSpeed Performance Report

Merging #441 will improve performances by 17.21%

Comparing Alex-Fischman:eval-lit-performance (840308a) with main (43de12f)

Summary

⚡ 2 improvements
✅ 85 untouched benchmarks

Benchmarks breakdown

Benchmark main Alex-Fischman:eval-lit-performance Change
eggcc-extraction 5.5 s 4.7 s +17.21%
string_quotes 475.3 µs 431.6 µs +10.11%

@Alex-Fischman Alex-Fischman deleted the eval-lit-performance branch October 16, 2024 02:55
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.

3 participants