.223 secs is a little less than half of what I get on one system, but on another I see less than .002 secs
On Wed, Jan 23, 2019 at 11:54 AM Gord Tomlin < gt.ibm.li...@actionsoftware.com> wrote: > On 2019-01-23 11:39, Kirk Wolf wrote: > > RESOLVER_TRACE=STDOUT host 127.0.0.1 >restest1.txt > When I use the above test command, I am consistently seeing about a > 0.22-0.23 second delay between "Resolver Trace Initialization Complete" > and "res_init Started", for example (lines without time stamps excluded): > > ******************************************************* Top of Data * > - - - - - - - - - - - - - - - - - - - - - - - > Resolver Trace Initialization Complete -> 2019/01/23 12:42:51.224214 > - - - - - - - - - - - - - - - - - - - - - - - > res_init Started: 2019/01/23 12:42:51.454687 > res_init Ended: 2019/01/23 12:42:51.454848 > - - - - - - - - - - - - - - - - - - - - - - - > GetHostByAddr Started: 2019/01/23 12:42:51.455411 > - - - - - - - - - - - - - - - - - - - - - - - > GetHostByAddr Ended: 2019/01/23 12:42:51.504890 > - - - - - - - - - - - - - - - - - - - - - - - > ****************************************************** Bottom of Data > > I don't see an extra long delay on the first test I perform in a session. > > -- > > Regards, Gord Tomlin > Action Software International > (a division of Mazda Computer Corporation) > Tel: (905) 470-7113, Fax: (905) 470-6507 > Support: https://actionsoftware.com/support/ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
