In some cases the CLI command is executing more than 30s, it depends on under which iDash user is authenticated.
In our case, we have >2 users in iDash (No EEM, No AD) with the same configurations and permissions. However, the execution time under the all users more than 30s except user "root", the execution time is ~1s.
-----
[root@******~]# time idlist -t user
aiun
anthonyk
idashAdm
root
real 0m1.251s
user 0m2.550s
sys 0m0.537s
-----
aiun@****** [~]$ time idlist -t user
aiun
anthonyk
idashAdm
root
real 0m31.324s
user 0m2.094s
sys 0m0.509s
Release : 12.1
Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7
In this case, a different JAVA was used for different users.
aiun@***** [~]$ which java
/opt/CA/WorkloadAutomationAE/JRE_WA/bin/java
[root@***** ~]# which java
/opt/CA/idash/jre/bin/java
Repointing JAVA PATH to /opt/CA/idash/jre/bin/java solved the issue with performance
aiun@****** [~]$ time idlist -t user
real 0m1.380s
user 0m2.893s
sys 0m0.508s