-
Notifications
You must be signed in to change notification settings - Fork 38
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
Performance issue when many columns displayed #913
Comments
Hello @gioeau Even though we do have virtualization on the rows of the table and it performs really well (can find it here with 100k elements), the big amount of columns can really mess it up. What user is expected to do with 100+ columns in the table? Let me know if there is anything else we could help with. |
Just to add on, you can also consider adding a column manager (example) to show only a subset of columns at any time. If you feel that the column manager has some missing features for your use case (since you have many columns), you can voice your thoughts on a related issue (#783). You can also try some suggestions mentioned in a similar issue about trying to improve the Table's performance (#888 (comment)). This might be pertinent because some of the performance issues in your playground is coming from the many rows rather than just the many columns. |
Yeah, column manager is probably the right move here. I don't think there's a good solution for performantly displaying hundreds of columns at the same time. This is a UX issue as much as a technical issue. |
Describe the bug (actual behavior)
When many columns are added to the table (in the hundreds), performance is hit severely.
Expected behavior
Performance shouldn't be hit so much by the number of columns in the table.
Reproduction
https://codesandbox.io/s/itwinui-react-minimal-example-forked-p1q6ih?file=/src/App.tsx
The text was updated successfully, but these errors were encountered: