Today, a client who uses their app in production requested an analysis of WU consumption in their application. Initially, upon examining the monthly chart, I deduced that there was some significant database import on 06/05. However, upon closer inspection, more than 70% of the consumption was from the “is on the last page” function, which is NATIVE to the repeating group. Since it is a Boolean function, why is there so much consumption when pagination is enabled?
Have you checked if your application uses this function and is also experiencing this consumption?
Here is the evidence for analysis below:
2 Likes
That does seem strangely high.
Behind the scenes, ‘is on the last page’ is doing a search for Things and charging WU accordingly. What’s in your RG’s data type? Is it a heavy data type? Are you storing images in it as text? Just throwing out ideas to see if we can get to the bottom of it for you.
Actually, I don’t have an image in this table. It’s just a simple table with name, description, and numerical values. Therefore, this consumption by this function doesn’t make any sense.
Can you send a link to the app? Private or public, I’d like to checkout what’s happening on the network side.
The index of the page on in a list should be a client side thing…the list is already pulled.
I guess my only idea would be if this is a single item or smaller count displayed RG and potentially every page swap it’s hitting the server to pull the record & hitting the server to get total record count to determine if it’s on the last page (not storing or caching the max count). Which they charge us 0.015 per record pulled so you can imagine that would add up fairly quickly to keep getting that max count.
Nothing outside of bad bubble optimization really makes sense to me on this one 
I got the same issue. It is was like that for a few months.
Had to rebuild pagination to infinite scrolling and remove counts from here and there as half of my 4.5 mln wu came from 3 counts.
And they said aggregated search is cheap. Cheat more like it 
The list is NOT pulled to the front-end. Everything is paginated and to know how many things the list countains you need to count it.
From that, it CAN MAKE SENSE that a apparently simple information like “is on the last page” can take huge amount of WU for counting stuff.
Since OP did not send more info about the datasource of the RG, then we should assume there is no bug but a highly complex formula.
5 posts were split to a new topic: Abnormal WU consumption?
