gregnb / gregnb/mui-datatables

rendering slow if data is provided by web sockets which are polling every sec.

Open
#1,138 6 comments 0 reactions 0 assignees View on GitHub
new feature performance
Dominant language
JavaScript
Stars
2.7k
Forks
906
PR merge metrics
No merged PRs in 30d

Description

i am feeding the mui data table with the data from web sockets( every sec 400 rows of data is being fed to table) and data table is performing very slow. not sure if it is because of column filters( filters will be calculated dynamically so this might be an issue i assume)

Below is the code i am using.




{stableSort(rowsData, getSorting(order,orderBy))
.slice()
.map((row,index) => {
return (

{cols.map((column,index) =>
{row[column.id]}
)}

);
})
}



Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Table/TableBody example in the issue and trace how the one-second websocket updates reach stableSort, dynamic filters, and the mapped rows. Reproduce the case with roughly 400 rows per update, then identify and verify the rendering bottleneck. Done means the table remains responsive under that update rate without changing the displayed data.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.