Skip to content

chore: add performance marks to track grid row rendering#10763

Closed
vursen wants to merge 1 commit intomainfrom
grid-user-timings
Closed

chore: add performance marks to track grid row rendering#10763
vursen wants to merge 1 commit intomainfrom
grid-user-timings

Conversation

@vursen
Copy link
Copy Markdown
Contributor

@vursen vursen commented Dec 25, 2025

Description

This PR adds performance marks to show in the DevTools where column tree and row rendering starts and how long it takes:

Screenshot 2025-12-26 at 10 10 50

Type of change

  • Chore

@vursen vursen changed the title chore: add User Timing marks for grid rendering chore: add User Timing marks for grid row rendering Dec 25, 2025
@vursen vursen changed the title chore: add User Timing marks for grid row rendering chore: add performance marks for grid row rendering Dec 25, 2025
@sonarqubecloud
Copy link
Copy Markdown

@vursen vursen changed the title chore: add performance marks for grid row rendering chore: add performance marks to track grid row rendering Dec 25, 2025
@vursen vursen marked this pull request as ready for review December 26, 2025 06:07
Copy link
Copy Markdown
Contributor

@DiegoCardoso DiegoCardoso left a comment

Choose a reason for hiding this comment

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

Do you believe it is worth calling performance.clearMarks()/performance.clearMeasures() somewhere?

@vursen
Copy link
Copy Markdown
Contributor Author

vursen commented Dec 30, 2025

Do you believe it is worth calling performance.clearMarks()/performance.clearMeasures() somewhere?

Good question... I'm not sure I have the answer...

@vursen vursen removed the request for review from web-padawan December 30, 2025 13:35
@vursen vursen marked this pull request as draft December 30, 2025 13:35
@vursen vursen closed this Jan 13, 2026
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