Thanks for the comment. How would you do the profiling? I’m afraid I have no experience doing that.
To be clear, even with just one table, it gets very slow when I add the onDefaultFiltered function (that is the culprit, much like the stackoverflow link). It is my impression that onFetchData happens behind the scenes and the suggested solution is to overload it.
My guess of what’s going on is that react-table filters the table on user input (everytime I press a key), but then notices that the defaultTableFilter has changed (as reagent notices the component depends on the atom that just changed), then tries to render the table once again - so two filters and renderings everytime I press a key instead of just one.