Skip to main content
Question

Dashboard Performance

  • Nov 10, 2026 8:59 PM UTC
  • 3 replies
  • 33 views
  • Translate All

dalesimmerly58
Pro I
Forum|alt.badge.img+1

Our company is trying to come up with some standard for dashboard use and design 

  • is the performance of a widget more dependent on the type of widget or the underlying GI
  • what are their widgets that use more resources than others?
    • what are widget that use the most resources / least 
  • are their any ways to measure dashboard usage over time (user views)
  • is there a recommendation on the max number of widget to include on DB?

Has anyone elected to use a application outside of Acumatica for analytics?

Does anyone use a constant other than their VAR for analytics 

 

Any thoughts along these lines would be appreciated 

 

 

 

3 replies

BenjaminCrisman
Acumatica Employee
Forum|alt.badge.img+4

​@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

Translate

willhowardnz
Freshman I
Forum|alt.badge.img

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?

Translate

Forum|alt.badge.img+11
  • Captain II
  • Nov 17, 2026 4:48 PM UTC

​@dalesimmerly58 

 

I have been on a ‘crusade’ recently to make our dashboards more efficient, with some currently taking a minute or 2 to load. These are currently the home screens for each department.

 

Alongside ​@willhowardnz suggestion to use the data warehousing feature from 26R2 onwards, I’d also recommend using PXProjection DACs. These can greatly improve the times that it takes to load data for dashboards but can also take a considerable amount of time to be produced. i.e. we have circa 80k BOMs and some generic inquiries look at the BOM cost history, and after just two cost rolls we are already up to 160k records. A PXProjection GI took our loading time for this specific GI from 2300ms to ~970ms.

Translate