hello,

thanks for the information.
the lookup depends on dns cache but I also don’t think it has a problem.
I think the negotiation process is innocent.
plan9 auth negotiation is fairly simple, that needs only a single step:
        C→A:  ticket request
        A→C:  encrypted ticket
I measured the times that are required for the auth server to complete the 
ticket request.
they are only a few milliseconds.

dialing time from client  to auth server is the problem.


> 2016/05/19 2:03、Skip Tavakkolian <[email protected]> のメール:
> 
> i don't think it's the auth lookup:
> 
> supermic% time ndb/csquery /net/cs net!luna.nyx.link!ticket
> /net/tcp/clone 115.36.102.252!567
> /net/tcp/clone 2402:6b00:4040:b600::8!567
> 0.00u 0.00s 0.34r      ndb/csquery /net/cs net!luna.nyx.link!ticket
> supermic% time ndb/csquery /net/cs net!grid.nyx.link!cpu
> /net/tcp/clone 115.36.102.252!17010
> /net/tcp/clone 2402:6b00:4040:b600::9!17010
> 0.00u 0.00s 0.01r      ndb/csquery /net/cs net!grid.nyx.link!cpu
> supermic% 
> 
> i suspect it's auth negotiations.
> 
> 
> 
> On Wed, May 18, 2016 at 6:07 AM Charles Forsyth <[email protected]> 
> wrote:
> 
> On 18 May 2016 at 01:43, arisawa <[email protected]> wrote:
> -                       p = netmkaddr(nt->val, netroot, "ticket");
>                         rv = dial(p, 0, 0, 0);
>                         if(rv >= 0)
>                                 break;
> 
> +                       p = netmkaddr(nt->val, “tcp", "ticket");
>                         rv = dial(p, 0, 0, 0);
>                         if(rv >= 0)
>                                 break;
> +                       p = netmkaddr(nt->val, “il", "ticket");
> +                       rv = dial(p, 0, 0, 0);
> +                       if(rv >= 0)
> +                               break;
> 
> But that's just (eventually) moving the cs search into every application and 
> bound to specific network types.
> Why is the cs search with "net" so slow?


Reply via email to