Welcome to Bubble (woo!)
The first thing you can do is lighten the ‘datas’ dataType. Does it have a lot of fields? The more bytes of data you are returning from the database the more WUs you’l consume. If its a heavy dataType you could create a Search DataType linked to ‘datas’ which just contains the data you need for the table.
If the data you have doesn’t change too often you could use Local Storage to store the data instead of the database. This is not a native bubble feature but there are plugins / simple Javascript to do this.
You could also use @gaimed’s WU Reducer
Potentially there are also ways to get the table to populate using a single search instead of running a search per cell.
Sounds crazy, but this can be done either by ‘delegating’ some work to the Client side (You could run a search to fetch all data needed for the whole table. Ideally you would sort in a way which could be mapped onto the table using item#, but if not you can use client-side filtering).
A more advanced technique would be to actually summarise the entire table content in a single Thing, using a new DataType. This datatype would have a text field that contains all the numbers in the table, as well as another field containing the list of dates, as well as one for the categories. This can have huge WU savings, but it can be hard to handle.
Optimisation has many factors, and optimisation can lead to over-optimisaton. Optimise a feature of your app too much, and another part of your app will become more complex/hard to handle.
Is this table the only place in your app where you are fetching this data? Are you just displaying the data? Do you want to allow for filtering/sorting?
So, before you go and optimise this table so that it only takes one search, what exactly is this table showing? Can you give a high level description of what the table + your app is actually doing?