[EuiDataGrid] track re-renders from hooks

[chandlerprall]

The data grid relies heavily on React hooks to maintain/cache various states and values. In many cases it is trivially simple to trigger unnecessary re-computations and re-renders of these hooks. The data grid should be given a new debugPerformance prop that, when enabled, console.logs when various hooks trigger, and ideally can provide a reason.

There are some existing browser/react extensions/hacks that can provide the same or similar information, but requiring setting those up, especially for downstream projects like Kibana, are complicated and time consuming.

[timroes]

Alteranatively we could evaluate using the performance API where it might be more appropriate.

[alexwizp]

@VladLasitsa cannot assign it to you, but could you please take it?

[VladLasitsa]

Ok, I'll take it, but I can't assign it to myself either

[stratoula]

Done 😉

[alexwizp]

I'm just curious why we cannot profiling EuiDataGrid component with the Chrome Performance Tab / DevTools Profiler. It just seems to me that maybe these logs will only annoy the person who really focuses on fixing performance problems.

[chandlerprall]

I'm just curious why we cannot profiling EuiDataGrid component with the Chrome Performance Tab / DevTools Profiler. It just seems to me that maybe these logs will only annoy the person who really focuses on fixing performance problems.

With heavy hooks usage for caching computed values, it isn't enough to know when a component re-rendered, but if a useMemo fired. I've added and removed console.logs to the hooks numerous times to try and track down a rendering performance issue, and it would be helpful to have a more permanent solution.

[github-actions]

👋 Hey there. This issue hasn't had any activity for 180 days. We'll automatically close it if that trend continues for another week. If you feel this issue is still valid and needs attention please let us know with a comment.

[chandlerprall]

This is definitely something we still want. Leaving unassigned in case someone else is interested in picking it up before we can get to it.

[github-actions]

👋 Hi there - this issue hasn't had any activity in 6 months. If the EUI team has not explicitly expressed that this is something on our roadmap, it's unlikely that we'll pick this issue up. We would sincerely appreciate a PR/community contribution if this is something that matters to you! If not, and there is no further activity on this issue for another 6 months (i.e. it's stale for over a year), the issue will be auto-closed.

[github-actions]

❌ Per our previous message, this issue is auto-closing after having been open and inactive for a year. If you strongly feel this is still a high-priority issue, or are interested in contributing, please leave a comment or open a new issue linking to this one for context.