[EuiDataGrid] Fullscreen browser rendering performance in Chrome

[kertal]

When using Chrome 83, MacOS 10.16.4, I'm experiencing high CPU load, laggy interface by hovering rows in full screen mode. It starts with setting the number of rows to 50, and when setting it to 100 it looks like this:

Used the docs for this: https://elastic.github.io/eui/#/tabular-content/data-grid

This is not the case in Firefox, and if I test it on a non-retina monitor it's much better (Just a quarter of the pixels to render, obviously). However seems that a simple hover takes much more CPU than in other browsers, so it's worth investigating.

Here's a screen of the Chrome performance tools:

And here's the profile:
Profile-20200708T082241.json.zip

[timroes]

I can reproduce that behavior in Chrome Linux, even on a low-dpi screen. But what feels even more laggy is switching the page size from let's say 100 to 50 or 10 to 50, will cause a couple of seconds to render this.

[sulemanof]

I'm experiencing the same issues, switching the pages, when there are 50+ rows per page. Reproducible in any browser. I'm on Windows 10.
Here is the performance snapshot of switching from 1st to 2nd page of grid in docs example https://elastic.github.io/eui/#/tabular-content/data-grid :

As far as I can see it on the snapshot, the performance drawdown mostly depends on amount of nodes and the heavy calculation of tabbable utility (takes around 200ms).

[kertal]

Seems .euiDataGrid__verticalScroll is causing this poor performance of hover cells in Chrome, seems to be normal when deactivating: overflow-y & height

Of course this is not the solution, since pagination disappears and scrolling doesn't work, but it's a trace. And Discover with DataGrid is also rendered this way

[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.

[github-actions]

❌ We're automatically closing this issue due to lack of activity. Please comment if you feel this was done in error.