SLOW loading dashboards in AccessPoint

[#1]

We have a dashboard that is literally taking more than 1 minute to load in AccessPoint. I have the dashboard PreLoaded into memory, so I just don't understand why AccessPoint takes 1 minute to display the Home sheet to the user when it's already loaded into memory. I've downloaded and run Rob Wunderlich's AWESOME Document Analyzer v2.qvw on the dashboard and so now I can clearly see the objects that are larger in size, objects that have longer calc times and objects that use the most memory bytes. So, what should I focus on in terms of getting the dashboard to load faster? Objects size? Calc Times? Memory Usage? I've tried to work on all 3 but, we're just not seeing any improvement in the load time. Maybe there is something else I should be looking into? Also, is there a QV log where I can see exactly what AccessPoint is doing that whole 1 minute it is taking to load the dashboard. If I could see what the heck AccessPoint is doing that whole 1 minute, I could figure out what needs to be tuned.

[#2]

Hi Paul,

Im having the same issue as I  have a massive Dashboard with lots of users and section Access and tons of tables/ and calcs in it. Please share if you got some workaround...

Thanks

Saileela Maguluri

[#3]

The Document Analyzer v2 helped as we focused on objects that we're large and took a long time to calculate. We focused on eliminating dimensions that had LOTS of data points. We had a chart that had a date dimension that could go back years, creating a dimension with 1,000's of data points and was causing BIG problems.

But probably the BEST thing we did to help, was we split our QV services onto 3 servers. We put QVS on it's own server. QVWS on it's own server. And then QMS, DSC and ReloadEngine are on another server. When we split the services onto different servers, it made ALL the difference in the world!!! Both in terms of speed and manageability because we're able to isolate problems now down to the service and we can start / stop services without it affecting the others. I would HIGHLY recommend splitting the services onto 3 servers to anyone doing a large scale QV implementation.

[#4]

Awesome Paul Thanks Much for sharing these tips. I shall try these and see how it goes....

[jfkinspari]

Hi,

How did it go with optimizing the load time of the Section Access heavy document?

Would be happy to get some tips

Thanks!

[davidg_curs]

@Paul Graeve

Could you describe in few words how you make a split of services over the servers?

Thanks