Most probably, Canvas will not provide a lot of improvement. Existing JS solutions (SVAR, DHTMLX, and Bryntum) already monitor which parts of the final chart are visible and render only those. The algorithm that selects data to render is the real bottleneck on big datasets, not the rendering itself.
As for WASM, the scheduling part may benefit a lot from moving to WASM. From similar projects in the past, it may give a 2x-3x boost in calculation speed, minus the time spent on sync between JS and WASM models. On large datasets, the time for data sending (serialization and deserialization) can consume a significant chunk of the gained boost.
mkozhukh 40 days ago. link 1 point ▲ ▼