1 of 1 people found this helpful
There's no overthinking this one as there's a lot that goes into optimal performance . What do render timings look like in your environment currently? Much of this you can get from the built-in dashboards.
Here's my method to the madness. Let me know if you want more details in any of these and I'm happy to share any workbooks that may be relevant. Seriously, I spent excessive time on tuning / transparency into the metrics during the first half of 2017. And now we're typically under 5 seconds average rendering time across about 3000 dashboard rendering on a daily basis.
1. make sure that infrastructure has necessary capacity in terms of CPU, BIOS clock speed, RAM, disk, network, and available threads. Out of all of these, in our environment, we ran into BIOS, available thread, and on occasion network constraints and adjusted how each is handled.
2. configure processes, caching, etc. - none of these seem to have any significant impact (> 1 second) on rendering performance, however we did make adjustments just to have the confidence for our shop that things were optimal
3. Look at long running dashboards that are most hit throughout the day. Then tune the data access in order to trim down the average daily rendering run time. This is what Alan Eldridge's best practices for performance focuses in on and this is often the first place to look assuming that #1 and #2 are not running into issues