Tiny datasize with long refresh time OR Large datasize with short refresh time?

[mpataki32]

What is better in terms of costs:
 

Scenario A) To have a smaller dataset (250 Mbyte) but having longer refresh time (15 minutes) for the dataset in PBIS.

Scenario B) To have a larger dataset  (544 Mbyte) but having short refresh time (5 minutes) for the dataset in PBIS.

The refresh of the dataset will be done once in a day. 

[Jai-Rathinavel]

@mpataki32 I would prefer Scenario B since I would have data which can be used to create reports with new requirement in the future and dataset of 500 Mb or 250 Mb size would not make much a difference on the cost.

[mpataki32]

Thank you @Jai-Rathinavel,

Thank you for your answer, to be honest we are making this change (the original report was 800 Mbyte), because we are expecting explosion in the dataset (new data acqusition) and I want to avoid to reach the 1 Gbyte threshold if it is possible, but tbh at first go I preffered the 500 Mbyte version as well.

[lbendlin]

Cost  (aka CU) is a combination of duration and computational complexity.

No need to guess - compare the CUs produced by either version and then pick the one with lower CUs.

[mpataki32]

Hi @lbendlin, 

I had that feeling that the duration is a factor as well, so I am going to dig myself into that. Thanks for that. One question: probably an admin page is required to see the computional information? 

[lbendlin · Accepted solution]

You see that in the Fabric Capacity Metrics App.