Mutu, there are few thing you could do to troubleshoot your Dashboard.
If nothing of the above works, then you have to do some homework to improve the performance.
1.- For each one of the WSDL that bring data from Webi reports, you will have to map QUERYRUNTIME and FETCHEDROWS from the output value (those are the last fields availables) and bind into the excel mdoel...Once you have that data for each QaaWs, you would know for sure which one is causing more delays either for the number of row being fetch or for any other reason. I believe only one qaaws may be causing the delay....
Being said that, let me ask you...How many rows each QaaWS is bringing from Webi? You shouldn't bring many rown or you will make the model really slow.
2.- With a watch measure the time each QaaWS is spending, for that you will have to disable all QaaWS and enable one at the time, preview and measure. The Dashboard will throw errors, but you will know which one you will have to twick.
3.- As a second tip, there are some parameters in the INPUT VALUE area that controls if the WEBI report should be refresh first, before bringing the data thru the QaaWS, make sure REFRESH is bind to FALSE cell in the excell model and if the webi repots are scheduled, then use GETfromLatestDOCUMENTinstance bound to a cell with a TRUE value.
4.- You could also install one add on into your web browser to verify how long are taking each one of the calls made to the QaaWS... We used fiddler2.com/home
Fiddler is a free web debugging tool which logs all HTTP(S) traffic between your computer and the the web server. It opens a line in the bottom of the browser and tells how longit last each call...It is very usefull...
Calling different QaaWS for different Webi reports, it would make the system to validate the authorization of the current user against the webi report that the dashboard is trying to pull the data. We prove this in an early version, using QaaWS from two different webi reports, but the difference wasn't that much....it was varelly 1.5 seconds when it was very slow.
5.- Review QaaWs server in teh CMC and check the different parameters.
I hope it helps.
Reinaldo