React virtual grid performance

[hareacostica]

• I have searched this repository's issues and believe that this is not a duplicate.

It has something in common with issue, but there version update did the trick. While updating to 1.9.1 no noticeable changes happen.

I'm using ...

• React Grid
• React Chart
• React Scheduler

Current Behaviour

The virtual grid performance is getting worse (in the shared example is noticeable that scroll gets slow, as well columns reorder) when adding more columns while having a lot of rows as well.

Expected Behaviour

The performance to not decrease that much.

Steps to Reproduce (for Bugs)

Created a codesandbox.

Environment

• devextreme-reactive: 1.8.0
• react: 16.6.3
• browser: Chrome 70.0.3538.110
• bootstrap: none
• react-bootstrap: none
• material-ui: 3.6.2

[SergeyAlexeev]

Hi,

Would you please test your demo in production mode? When you are using codesandbox, a demo is running in development mode. Also, you can check this demo. How does it work on your side?

[hareacostica]

Yes, its true, the grid is smooth in production mode, didn't think it will be such an big difference.
Still having lag spikes when data is updating, but not sure the issue is coming from the grid. So will investigate and come back with an update.

Thanks!

[hareacostica]

After checking why there is still lag spikes when data is updating, i noticed that instead of updating just some rows, everything is re-rendered again (i was using Highlight Updates from react dev tool).
I tried to create some custom components for Row and Cell where i prevent update if data did not update, but it still showed me that everything is re-rendered (created another demo, as the previous one had some issues while trying to install locally).

[SergeyAlexeev]

We've discussed a similar question in the context of these issues: #396, #1707. Please check them out.

[hareacostica]

@SergeyAlexeev Great. Thanks!

[lock]

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests.