Hi!
two big thumbs up on this request! We also have soffisticated workshop applications and struggle to understand what is driving the compute/costs of it.
A starting point for us the newly introduced profiler in workshop that is good to understand if one is actually calling only what’s necessary. However, this only gives us what’s called and the duration. I would really love to see the associated compute. Currently my assumption is, that variable querries which are taking longer are more expensive.
But at the end of the day, we actually have to do a lot of trial and error to identify how much certain functionalities really cost.
A lot of my daily work is at the moment creating copies of workshop applications (as xyz app name [cost test feature XYZ]) where I execute a certain defined scope of steps/interactions. I then wait a day for our resource app to have picked up data from previous day to see how much cost these few actions have incurred at aggregate. To then repeat the same with another subset of steps in order to try to interprete which step costed how much.
So you see that this is a very inefficient trial & error way of doing it, however I see no other choice at the moment.
Crossing all fingers that this gets on the roadmap soon!