* [9fans] ndb/cs seems slow (3 secs) @ 2014-03-07 12:57 Steve Simon 2014-03-07 13:04 ` erik quanstrom 2014-03-07 13:04 ` erik quanstrom 0 siblings, 2 replies; 5+ messages in thread From: Steve Simon @ 2014-03-07 12:57 UTC (permalink / raw) To: 9fans 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] ndb/cs seems slow (3 secs) 2014-03-07 12:57 [9fans] ndb/cs seems slow (3 secs) Steve Simon @ 2014-03-07 13:04 ` erik quanstrom 2014-03-07 13:04 ` erik quanstrom 1 sibling, 0 replies; 5+ messages in thread From: erik quanstrom @ 2014-03-07 13:04 UTC (permalink / raw) To: 9fans On Fri Mar 7 07:58:51 EST 2014, steve@quintile.net wrote: > 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: could it be choking on ip6? - erik ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] ndb/cs seems slow (3 secs) 2014-03-07 12:57 [9fans] ndb/cs seems slow (3 secs) Steve Simon 2014-03-07 13:04 ` erik quanstrom @ 2014-03-07 13:04 ` erik quanstrom 2014-03-07 13:28 ` Steve Simon 1 sibling, 1 reply; 5+ messages in thread From: erik quanstrom @ 2014-03-07 13:04 UTC (permalink / raw) To: 9fans >> I have traced the problem to ndb/cs, which seems to be taking >> about 3 secs to resolve a name: > >could it be choking on ip6? that is, does ndb/cs -4 give the same results? - erik ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] ndb/cs seems slow (3 secs) 2014-03-07 13:04 ` erik quanstrom @ 2014-03-07 13:28 ` Steve Simon 2014-03-07 13:48 ` erik quanstrom 0 siblings, 1 reply; 5+ messages in thread From: Steve Simon @ 2014-03-07 13:28 UTC (permalink / raw) To: 9fans Excellent! Good spot. For the archives, ipv6 can also be toggled on/off with echo ipv6 > /net/cs Thanks -Steve ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [9fans] ndb/cs seems slow (3 secs) 2014-03-07 13:28 ` Steve Simon @ 2014-03-07 13:48 ` erik quanstrom 0 siblings, 0 replies; 5+ messages in thread From: erik quanstrom @ 2014-03-07 13:48 UTC (permalink / raw) To: 9fans On Fri Mar 7 08:29:46 EST 2014, steve@quintile.net wrote: > Excellent! Good spot. > > For the archives, ipv6 can also be toggled on/off with > > echo ipv6 > /net/cs off by default might be the right thing on more systems than not. - erik ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-03-07 13:48 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2014-03-07 12:57 [9fans] ndb/cs seems slow (3 secs) Steve Simon 2014-03-07 13:04 ` erik quanstrom 2014-03-07 13:04 ` erik quanstrom 2014-03-07 13:28 ` Steve Simon 2014-03-07 13:48 ` erik quanstrom
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).