Why are CABI reports so slow to run

Article Id: 140243

Status: Published

Updated On: 15-11-2019 06:12

Products:

DX Infrastructure Management , NIMSOFT PROBES

Issue/Introduction:

Just wondering if there are any optimization tips for getting CABi to generate reports quicker?
UIM's CABI is the slowest reporting tool I ever used compared to other solutions that are out there.
I'm trying to run a Group Trend Report based on last 3 days, on just 6 boxes basically CDM metrics (cpu, disk, memory, in/out-bound traffic) and its been running for 15 min with the Please Wait...

Other larger reports take up to 45 min - 1hr+ to run based on 1 month data. Any tips here to get this working more efficiently?

Cause:

The default memory settings may not be enough to quickly run reports

Environment:

UIM 8.x 9.x

CABI 3.X 4.x

Resolution:

change the CABI and WASP memory parameters and this made the response time much better.

UMP wasp:

<opt>

java_mem_max = -Xmx6g

java_mem_init = -Xms2g

java_stack_size = -Xss64m

min_perm_size = -XX:PermSize=512m

max_perm_size = -XX:MaxPermSize=1024m

java_gc_conc_marc_sweep = -XX:+UseConcMarkSweepGC

java_cms_classunloading_enable = -XX:+CMSClassUnloadingEnabled

</opt>

CABI:

<opt>

java_mem_max = -Xmx6g

java_mem_init = -Xms2g

dump_memory = -XX:+HeapDumpOnOutOfMemoryError

</opt>