Comment 1 for bug 1829249

I did some test locally ,it takes 1 sec, from my expereince, it's unlikely be caused by zthin for long delay, it might be caused by zthin socket connect to SMAPI and lead to some network latency
and 0.1 sec you mentioned might be DIRMAINT only? as the time will be smcli -> SMAPI -> DIRMAINT (actually DIRMAINT is more slow, so SMAPI has an internal cache and return very fast)

IDENTITY OPNCLOUD XXXXXXXXX 8G 8G G
BUILD ON OPNSTK1 USING SUBCONFIG OPNCLO-1
BUILD ON OPNSTK2 USING SUBCONFIG OPNCLO-2
CPU 00 BASE
CPU 01
CPU 02
CPU 03
MACHINE ESA 4
IPL 190 PARM AUTOCR
IUCV ANY MSGLIMIT 512
OPTION LNKNOPAS
CONSOLE 0009 3215 T
SPOOL 00C 2540 READER *
SPOOL 00D 2540 PUNCH A
SPOOL 00E 1403 A
* END IDENTITY OPNCLOUD

*DVHOPT LNK0 LOG1 RCM1 SMS0 NPW1 LNGAMENG PWC20161220 CRC▒"

real 0m1.032s
user 0m0.001s
sys 0m0.001s

yes, it take some time and it do need some