Hi,
I’ve been doing a performance trace on a long running calculation view which is called from a query accessing a composite provider (with only this single calculation view). I noticed that the majority of the time is spent optimizing the model. What I can’t make sense of is the wait time …

If I add all the times from the activities below optimize model (assemble result and search on table/delta), I don’t get anywhere close to the total time for that step. The time difference is established because the large gaps of wait time highlighted below. From the PlanViz I don’t see any issues with memory consumption or network traffic … the only glaring bottleneck is the apparent wait time in the optimize step. PS – I did try force this to run exclusively on the SQL engine and it took much longer to run. Does anyone have ideas or suggestions?

Thanks,
Graham
Request clarification before answering.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.