Twitter search results table is very slow to manipulate and save

I’ve just started using the Twitter API Connector and Twitter Search nodes, and am finding that while they work fine, the resulting table takes ages to process and to save. For example, using the Table Writer, it takes about two and a half minutes to save an output table containing 4,100 rows. The resulting file is just 700kb. Similarly, if I perform a simple operation such as adding a constant value column, this takes many time longer than usual.

If I load the saved table, or run it through the Cache node, it handles very quickly, just like any other table.

What is going on here? And is there any way it can be made to work more efficiently?

Hi sugna,

could you share an example workflow? That would really help to reproduce and investigate this. Maybe there is a workaround to make it faster.