<DataGrid /> is designed from the ground-up to be very fast and efficient with big datasets. If you can fit a dataset into the browser without making it freeze, then handling it through the
<DataGrid /> will be by no means worse.
Besides being able to render huge amounts of data (and therefore very many rows), the grid is also built to support a big number of columns. Although in most cases 10 columns or less are enough, the
<DataGrid /> can handle about 50 columns quite easily.
In order to make the component zippy while handling and displaying so much data, virtualization has been used extensively. Virtualization is used for both the rows and for the columns (in case there are many columns).
<DataGrid /> peformance mostly refers to how the
<DataGrid /> behaves & updates while scrolling - since this is the most performance-sensitive operation one can do with a
In case you run into a performance issue, the first thing you need to check is whether you're updating
<DataGrid /> props unnecessarily.
To boost performance of the
<DataGrid />, we treat props as immutable and only update the
<DataGrid /> when you pass different props.
So for example, to improve the rendering performance, make sure you pass the same reference to a
when rendering the
, instead of building the dataSource in the render function of your app and passing it new each time to the
, even when the
If the performance issue still persists, you might try to increase the default
. The less rows fit into the viewpot, the snappier the
In case you have many columns, and the
<DataGrid /> performs column virtualization, try increasing the widths of
<DataGrid /> columns in order to improve performance. The less columns fit into the viewport, the snappier the
<DataGrid /> is.