This is probably due to somthing silly I have done, I am trying to debug
why my machine is being slow to dial network connections.
I had just got used to it until I have reason to use sshnet to a linux box
which seemed much faster.
I have traced the problem to ndb/cs, which seems to be taking
about 3 secs to resolve a name:
larch% echo tcp!www.bbc.co.uk!http | time ndb/csquery
> /net/tcp/clone 212.58.244.67!80
/net/tcp/clone 212.58.244.66!80
> 0.00u 0.00s 3.07r ndb/csquery
However, if given an IP address it is quick:
larch% echo tcp!212.58.244.67!http | time ndb/csquery
> /net/tcp/clone 212.58.244.67!80
> 0.00u 0.00s 0.01r ndb/csquery
I have checked dns which resolves names quickly:
larch% echo www.bbc.co.uk | time ndb/dnsquery
> www.bbc.net.uk ip 212.58.244.66
www.bbc.net.uk ip 212.58.244.67
> 0.00u 0.01s 0.20r ndb/dnsquery
I remember that there where some changes ages ago to support /net.alt
but I don't have one. I do have a /net.home, my own creation, but cs
doesn't know about that (unless it is cleverer than I thought).
Anyone have any ideas where to look next?
-Steve
