Dashboard Performance

​@dalesimmerly58 

The performance of any widget will be related to specifically the GI it is tethered to. The widget itself is not going to consume much, but if the query it represents is incorrectly built or contains many hundreds of thousands of records it needs to filter, it can take more time.

There is no single widget which will be more resource intensive than others, it’s just about the underlying data.

You can check Access History for how frequently a screen is visited, but there is no metric to count screen visits otherwise, that I’m aware of at least.

You can include as many as you want, but the more you have the slower it might load, it’s just a balancing game

Hi ​@dalesimmerly58 

Just additionally to ​@BenjaminCrisman ‘s excellent advice, things I warn clients for with dashboards:

1. If a Dashboard is someone’s homepage, all widgets load anytime they open Acumatica. 
   1. Try to only have widgets relevant to the staff there.
   2. Consider splitting different staff to different dashboards, rather than having 1 dashboard with a lot of information that many staff don’t need.
2. Think about the Filters for any dashboard widgets, get as little data as possible.
3. Optimize the underlying GI queries as much as possible
4. Where possible, use the longest refresh period you can. (Does the report need to be up to the minute, or would having a daily refresh each morning be good enough?)
5. In 26R2, you could consider using the data warehousing GI features to do pre-calculation for a bunch of dashboard information, this might help considerably.

For max DB widgets, I don’t really have one, that’s going to come down to the underlying GIs and refresh periods.  I would try to limit dashboards to just relevant information, what figures do staff actually use?