FUAM capacity usage on Fabric (F64 or other) – real-world experience?

[Lukasz (lebinho)]

Hi all,
I’m evaluating the Fabric Unified Admin Monitoring (FUAM) solution accelerator and I’m trying to understand its real impact on capacity usage before deploying it.
I’m currently running an F64 capacity and would like to avoid unexpected spikes or interference with production workloads.
From reviewing the repository and documentation, I understand that FUAM relies on pipelines, notebooks, and Lakehouse storage, but I couldn’t find any concrete guidance on:

Typical CU consumption (average or peak)
Impact during initial deployment vs. ongoing runs
How usage scales with tenant size (number of workspaces, activity volume, etc.)
Recommended scheduling approach to minimize impact

If anyone has implemented FUAM in a real environment, I’d really appreciate insights such as:

% of capacity usage observed
Whether it caused noticeable throttling or performance degradation
Best practices for scheduling and optimization

Thanks in advance!