Hi, 

In MAS 9.1.8, Operational dashboards performing slowly. OOB API calls related to MXAPIVIEWMANAGER taking more than 30/40 sec. 

Is there list of parameters to check?

Please advise, thanks.  

Hi Prathamesh,

Does the slowness occur on the default out‑of‑the‑box Operational dashboards as well, or only on custom dashboards/tabs (with added cards/saved views)?

Quick triage for slow Operational Dashboard (MXAPIVIEWMANAGER) – MAS 9.1.8

• Simplify the default dashboard: test with a minimal dashboard (few cards) to see if load time drops, then add cards back gradually.  
• Trim heavy cards/queries: KPI/Trend/Comparison and Work Queue cards execute queries; reduce trend windows and card count to isolate offenders.
• Check saved views/columns: MXAPIVIEWMANAGER returns view configs; many or complex saved views (wide column sets, related attributes) can bloat the call, keep selections lean, avoid deep dot‑notation.
• Client sanity check: use the browser Network tab to confirm which request is slow and its payload size; keep pageSize modest and avoid select=*.
• Log the real bottleneck: enable mxe.db.logSQLTimeLimit (e.g., 200–500 ms) and set the root logger to WARN so slow SQL is captured.
• Reference baselines: IBM performance best practices + MAS Performance Wiki (sizing/tuning/DB).

If you do not find anything above, check Environmental basics:

✅ Maximo Application Suite (MAS) Performance Check List

Kind regards

Anneli 
------------------------------
Anneli Dolff
Maximo Consultant
Nexer AB
Göteborg

Sweden
------------------------------