Hi all,
I wanted to share a small improvement to our workload attribution model for searches (including group by and aggregations). This update doesn’t change anything about how much workload your app consumes — it only updates how it’s attributed. For those of you who pay close attention to your app’s workload consumption on a daily basis, this might make things look a little different, so we wanted to flag here in advance.
What’s changing:
Previously, if a search was initiated in one element, and there was another element referring to that element’s state, that WU could be attributed to either element depending on how the elements are loaded, An example of this: A text element referring to a repeating group’s list, which also has an expression within a search.
Starting today, the workload will always be attributed to the original element that has the search. In the above example, it would be the repeating group.
How will this affect you?
For most users, this change will have minimal impact. However, if you monitor your app’s consumption daily, you might notice differences in how workload is reporting going forward. This update aims to make workload more reflective of actual usage.
We hope this adjustment will help improve your understanding of workload usage.
Thanks,
Laura