​Hi,

We just had an discussion internally wondering why the ISAM Management Api's is a bit slow.
Example:
https://[mgmt]/wga/reverseproxy/[instance]/junctions?junctions_id=[junction]

  time_namelookup:  0.031000
          time_connect:  0.047000
   time_appconnect:  0.266000
    time_pretransfer:  0.266000
          time_redirect:  0.000000
 time_starttransfer:  0.891000
                    ----------
         time_total:  0.891000

Almost 0.6 second for getting information about one junction. Why?

***************************************************************************************************************************

time_appconnect The time, in seconds, it took from the start until the SSL/SSH/etc connect/handshake to the remote host was completed. (Added in 7.19.0)

time_connect The time, in seconds, it took from the start until the TCP connect to the remote host (or proxy) was completed.

time_namelookup The time, in seconds, it took from the start until the name resolving was completed.

time_pretransfer The time, in seconds, it took from the start until the file transfer was just about to begin. This includes all pre-transfer commands and negotiations that are specific to the particular protocol(s) involved.

time_redirect The time, in seconds, it took for all redirection steps including name lookup, connect, pretransfer and transfer before the final transaction was started. time_redirect shows the complete execution time for multiple redirections. (Added in 7.12.3)

time_starttransfer The time, in seconds, it took from the start until the first byte was just about to be transferred. This includes time_pretransfer and also the time the server needed to calculate the result.

time_total The total time, in seconds, that the full operation lasted.

***************************************************************************************************************************

Regards

------------------------------
Mikael
------------------------------