Workload Units consume - Need help!

I’m trying to optimize my data usage, but among the expenses, I came across many doubts. However, the main one is shown in the W.U consumption graphs.**

In the image below, the graph shows 35,525 Searches, and 50% of that comes from just one repeating group that I use in a schedule.

My question is this: does the “Searches” shown in the graph refer to search actions in the database, returned items, or something else?

Because I find it hard to believe that the user has reloaded the page that many times to have made that many database searches.

I also experience this issue. May I for solution to this problem?

I’ve experienced something similar , my app was consuming around 1000 WU per minute and happen for an hour, which doesn’t make sense based on actual user activity


@magno @rodenair.yoonet you both may benefit from checking out my paid plugin Data Jedi. I did a test to fetch 51,200 items, make changes to all 51,200 items and it cost less than 45 WUs using the Hybrid Data Structure approach the Data Jedi plugin helps make super simple.

It is a bit of a mystery honestly. I have not really been able to pinpoint exactly what is displayed in those graphs as the labels are not consistent. Usually though for a search the number of WUs is representing how many items returned and how many characters of data returned, as that is what costs for a search to be performed. The number of times the search took place of 35,525 times is in my experience not an indication of how many times the search was performed. For example, an app of mine once consumed around 250,000 WUs a month for one search of 2,000 items. It showed in graph as being performed some 100,000 times or so, but when I drill down, it really was that there are around 20,000 visits to the page per month where the search is performed, and sometimes, the reloading of the page due to pagination, might have caused the search to perform again.

@runnel.yoonet That is a lot and scary. The Data Jedi plugin can help reduce the cost of fetching data by 95%. I do not use it for every single type of data or every single use case of any app, but over the past 4 months of using it, I’m finding less and less examples of where it doesn’t have benefit.

1 Like

This topic was automatically closed after 70 days. New replies are no longer allowed.