9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] cpu command latency
Date: Wed, 11 May 2016 22:39:38 +0000	[thread overview]
Message-ID: <CAJSxfmKPGRHowX1huGDcuXYxWN2soHzGHW1osKWbftWsvt_N_g@mail.gmail.com> (raw)
In-Reply-To: <2202C006-B0C9-40AE-B6FC-CA415D41A66A@ar.aichi-u.ac.jp>

[-- Attachment #1: Type: text/plain, Size: 1750 bytes --]

what's the latency caused by the auth step?
FYI, from Seattle I see about 8 seconds to establish but as Charles noted,
it's reasonably fast after that.


On Wed, May 11, 2016 at 2:05 PM arisawa <arisawa@ar.aichi-u.ac.jp> wrote:

> Hello,
>
> we can measure the latency that comes from network connection
> by executing simple program such as telnet or something others
> to the port 8006 of grid.nyx.link. the content is:
> #!/bin/rc
> cat $net/local
> cat $net/remote
>
> yes the DNS may make a problem in IPv4/IPv6 mixed environment.
> my server supports both IPs.
> the cpu command will select IPv4. the command does not have “-6” option.
> If we want to connect by IPv6, literal IP address is required in the
> argument of the command.
>
> Kenji Arisawa
>
> > In my experience, it's almost unfailingly the DNS that slows down
> > establishing an Internet session of any type.
> >
> > Lucio.
>
> > 2016/05/12 0:23、Kenny Lasse Hoff Levinsen <kennylevinsen@gmail.com>
> のメール:
> >
> > Well, based on the 9fs test that was posted, I'd think dial is being
> awfully slow.
> >
> > Maybe try something simpler? aux/listen1 echo hello and a simple network
> connection?
> >
> > Best regards,
> > Kenny Levinsen
> >
> > On 11. maj 2016, at 16.13, Charles Forsyth <charles.forsyth@gmail.com>
> wrote:
> >
> >>
> >> On 11 May 2016 at 14:44, Kenny Lasse Hoff Levinsen <
> kennylevinsen@gmail.com> wrote:
> >> Delete the channel from /srv in the loop to test a full remote mount
> dance, including the initial dial. It shouldn't take 3s to dial, though.
> >>
> >> There's something initially slow in connecting to  grid.nyx.link with
> cpu, and setting up, but once there it's fine.
>
>
>

[-- Attachment #2: Type: text/html, Size: 2392 bytes --]

  reply	other threads:[~2016-05-11 22:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11  9:04 arisawa
2016-05-11  9:23 ` Charles Forsyth
     [not found] ` <CAFSF3XOQY2rH2fRmFEV2d5vGbc6ONkVpRvKY=dR7AvorqB7aKA@mail.gmail.com>
2016-05-11 13:12   ` arisawa
2016-05-11 13:44     ` Kenny Lasse Hoff Levinsen
2016-05-11 14:13       ` Charles Forsyth
2016-05-11 15:23         ` Kenny Lasse Hoff Levinsen
2016-05-11 15:58           ` lucio
2016-05-11 21:05           ` arisawa
2016-05-11 22:39             ` Skip Tavakkolian [this message]
2016-05-12 13:18               ` arisawa
2016-05-12 15:40               ` Skip Tavakkolian
2016-05-12 16:00                 ` Balaji
2016-05-14 13:30                 ` arisawa
2016-05-18  7:31                   ` arisawa
2016-05-12 13:06       ` arisawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJSxfmKPGRHowX1huGDcuXYxWN2soHzGHW1osKWbftWsvt_N_g@mail.gmail.com \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).