![Screenshot_20231007_125400.png](https://files.peakd.com/file/peakd-hive/leoplaw/23t79FD1oBzNrTZ8E2ZdcoYoLwdfbfr4F9oWAyccmKiHKsMW4pwQrquScqQQ8QZrJKWrC.png)


In the quest for performance improvements, work is currently being done on how the chart calculates indicators.

The first improvement is having the chart only calculate the required indicator data instead of the entire price history when new chunk of back history data is added.

The chart currently uses [talib-web](https://github.com/ancheGT/talib-web) for indicator calculation. It is a port of the technical analysis library written in C, ported to WebAssembly. The current release of TradeX uses this library on the main thread. If there is a large price history to process, this can lead to the main JavaScrpt loop (thread) being blocked and causing the browser tab to unresponsive. So the option of moving the indicator calculation to a web worker, a separate thread to free up the main thread is being explored.

I now have the TALib-web wasm initializing on a web worker. This was quite a challenge and required a good deal of research and trying numerous options before a solution was found. In the end the simplest was best.

Next step is to call the TALib functions in the worker and have the results returned.
If that works, then I can finally do the following test comparisons:

1.    talib-web funciton calls on main thread vs  worker
1a.  browser comparisons of the above
2.    technicalindicators function calls on main thread vs worker
2.a  browser comparisons
3.    compare 1 and 2.

technicalindicators is another library, but is pure JavaScript (now wasm)
I want to see the wasm vs JS performance comparison.
The results might be surprising.