You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a use case for the DataTable which seems to be hitting some limits of the component.
My use case is that I have a table with 38 columns, which has thousands of entries hence it's connected with the back-end API to do the pagination and filtering.
We make use of PrimeReact filter UI with filterDisplay set to menu, now when trying to input a certain value in any of the one columns, the input handler takes time to take place, usually it's about 500ms for a simple input change. Which shows with this error: [Violation] 'input' handler took 528ms
Also, when the table first renders it shows similar messages but for different handlers, which are:
[Violation] 'setTimeout' handler took 545ms [Violation] 'message' handler took 492ms
When I'm running the profiler to find the bottleneck, I see that for each input change the whole table gets re-rendered. I think it's best to not trigger a full re-render until the Apply is clicked. That is one assumption that I have, if there is an option that I'm missing please let me know.
Describe the bug
I have a use case for the DataTable which seems to be hitting some limits of the component.
My use case is that I have a table with 38 columns, which has thousands of entries hence it's connected with the back-end API to do the pagination and filtering.
We make use of PrimeReact filter UI with
filterDisplay
set tomenu
, now when trying to input a certain value in any of the one columns, the input handler takes time to take place, usually it's about 500ms for a simple input change. Which shows with this error:[Violation] 'input' handler took 528ms
Also, when the table first renders it shows similar messages but for different handlers, which are:
[Violation] 'setTimeout' handler took 545ms
[Violation] 'message' handler took 492ms
When I'm running the profiler to find the bottleneck, I see that for each input change the whole table gets re-rendered. I think it's best to not trigger a full re-render until the
Apply
is clicked. That is one assumption that I have, if there is an option that I'm missing please let me know.Reproducer
No response
System Information
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: