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

[charts] Replace path with circle for perf improvement #14518

Merged
merged 11 commits into from
Sep 12, 2024

Conversation

alexfauquette
Copy link
Member

@alexfauquette alexfauquette added performance component: charts This is the name of the generic UI component, not the React module! labels Sep 6, 2024
@mui-bot
Copy link

mui-bot commented Sep 6, 2024

Deploy preview: https://deploy-preview-14518--material-ui-x.netlify.app/

Generated by 🚫 dangerJS against 344aa44

@flaviendelangle flaviendelangle changed the title [charts] Replace path by circle for perf improvement [charts] Replace path with circle for perf improvement Sep 6, 2024
Copy link

codspeed-hq bot commented Sep 6, 2024

CodSpeed Performance Report

Merging #14518 will not alter performance

Comparing alexfauquette:line-perf (344aa44) with master (4f2a244)

Summary

✅ 3 untouched benchmarks

@alexfauquette
Copy link
Member Author

I was disturbed that codespeed did not reported positive impact. But it seems ok

image

@JCQuintas
Copy link
Member

I was disturbed that codespeed did not reported positive impact. But it seems ok

image

We can change to a lower percentage, probably makes sense to make it like 3-5%

/**
* If `true` marks will render `<circle />` instead of `<path />` and drop theme override for faster rendering.
*/
markPerfUpdate?: boolean;
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
markPerfUpdate?: boolean;
usePerformantMarks?: boolean;

Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
markPerfUpdate?: boolean;
improveMarkPerformance?: boolean;

Copy link
Member

Choose a reason for hiding this comment

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

markPerfUpdate sounds vague, "update" is a status, so it doesn't fully describe the action I think.

Copy link
Member Author

Choose a reason for hiding this comment

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

What about experimentalMarkRendering To say it's planned to be the future default behavior in v8?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, I think that would be great

Copy link
Member

@JCQuintas JCQuintas left a comment

Choose a reason for hiding this comment

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

rerunning the tests as I didn't see the cause for them failing 🤔

@JCQuintas
Copy link
Member

To fix benchmarks #14573

@alexfauquette alexfauquette merged commit 7120da2 into mui:master Sep 12, 2024
19 checks passed
@alexfauquette alexfauquette deleted the line-perf branch September 12, 2024 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: charts This is the name of the generic UI component, not the React module! performance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants