Actually, I spoke too soon. I decided to run Wireshark again and see what it said. Launching the h2 console now only takes 58s as opposed to the 1m25s of previously. Still too slow, but an improvement. (The reason I originally said there was no improvement is that unless I'm doing something like a trace, these days I don't bother waiting for the console to grind its way to completion: if it doesn't finish launching in a matter of seconds I quit it.)
Two differences that I can see in the Wireshark trace: 1) There are none of the "Standard query 0x0000..." rows. 2) There are no packets at all added to the window until the point where "Console" appears in my menu bar. This is after 22s -- so, essentially the same time-lag as previously. But there is (apparently) no network activity now during the lag. ????? OTOH, I am still having the same local hostname resolution problem. Running the inetTester <https://github.com/thoeni/inetTester> still produces a result of just over 5s. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
