Cairo codes which generates huge instruction tables or execution trace causes performance lags in low-spec devices as thousands of rows renders into the Browser DOM and even one re-render causes all those thousands of rows to render again which causes performance lags and in fact might crash browsers in some very low end devices.
We can improve this drastically by introducing Virtualized Rendering in Execution Trace as well as Instruction Table.
Virtualized rendering will only render certain amount of rows which are visible in the browser window and render rest of the rows dynamically while scrolling.
I would like to work on this.
Cairo codes which generates huge instruction tables or execution trace causes performance lags in low-spec devices as thousands of rows renders into the Browser DOM and even one re-render causes all those thousands of rows to render again which causes performance lags and in fact might crash browsers in some very low end devices. We can improve this drastically by introducing Virtualized Rendering in Execution Trace as well as Instruction Table. Virtualized rendering will only render certain amount of rows which are visible in the browser window and render rest of the rows dynamically while scrolling. I would like to work on this.