My first area I would want to focus on is how to improve the loading performance of the slower CVs, What things are slowing them down? Things like too many rows/columns and member formulas that are dynamically calculated can adversely affect reporting performance, the latter being significant in it's effect on query performance. 15 seconds to load a CV seems excessive.
A bit of everything. Granular balsh report; with E#Entity.Tree expansions; lots of time views for comparing CurMth to PrMth, and to Forecast, with variances. All per user request.
They are fine with the longer initial load time if it means they have the data available for analysis. But the switching back and forth between tabs is what is frustrating them due to the full re-run of the CV.
