Performance - Split data before collecting or collect with filter

[Anonymous]

Is there any performance difference between having your data in one table and collecting it with a filter:

Collect(Collection1,Filter(Datatable,Field1 = "value1"))

or would it be better to split the data into multiple tables and collect the table you want at that time? I am not sure if powerapps still has to parse all of the rows in the table or does the filter make the performance equal either way. If more details is needed, assume the data is from a dataflow/stored in a dataverse table and has 14,000 records (or seven ~2,000 records split by State in the 2nd option).

[v-jefferni]

Hi @Anonymous ,

Without considering delegation issues, collect filtered records from a single table would definitely have better performance. While if filtering by non-delegable functions/columns, you will have to collect all the records from the split tables.

Please refer to the blogs about delegation written by Warren:

https://www.practicalpowerapps.com/category/delegation/

Hope this helps.

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.

[Prakash4691]

@Anonymous ,

It is better to have it in single table instead of multiple tables.

When it comes to performance improvement for dataverse, if there are any filtering condition needed for static values like checking with option set or any text, it is better to handle filtering condition in view i.e. on server side instead of client.

And in gallery select that view and filter applies automatically, do not want filter explicitly in canvas app using filter function.

Give thumps up and mark it as solution, if it answers your question.

Regards,

Prakash

[Anonymous]

Let me clarify. The original data is stored in an Oracle database. I am using a dataflow/power query to get the data into a dataverse table. In that same process I can split the data by State to make seven tables (seven states). In the powerapp they choose the State first before any data is collected so I would be collecting just that states table, not multiple states/tables. This is extra work to split the data but its on the dataflow side (server).

The other option is to put all of the data into one table but collect it in the app with a state filter which is easier to implement. I would think this would be slower but not sure if the Filter would make the loading performance the same. 

[Prakash4691 · Accepted solution]

@Anonymous ,

If state filter is static you can handle that filter in server(dataverse) side itself. In canvas app just pull the data.

If it is dynamic, it all depends on number of data + number of fields used inside filter for the performance. If it is just one field I don't think so performance would impact.

When it comes to dataverse you will have lot of option to do filtering part in view and referring that view inside app for less impact in performance.

Mark it as solution, if it answers your question.

Regards,

Prakash