At present, Tulip’s interactive table widget automatically subscribes to the data updates of the associated table / variable. In our observation, this can become a significant resource hog because Tulip will constantly redraw the UI; particularly if multiple table widgets need to be displayed and the underlying data is changing rather often.
Unless there is a way to improve the refresh and display of data to be less resource intensive, a possible alternative would be to explicitly allow for an option to disable auto-updates and in this case switch to a pull-data approach instead. At present this can be achieved by fetching the required data via a Table API connector call and thus making the result a static variable. But this is a significant development overhead and hence reduces one’s ability to quickly adapt to changing user needs.
