Re: [9fans] cpu command latency

2016-05-11 Thread Skip Tavakkolian
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 wrote: > Hello, > > we can measure the latency that comes from network connection > by executing simple

Re: [9fans] cpu command latency

2016-05-11 Thread arisawa
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

Re: [9fans] cpu command latency

2016-05-11 Thread lucio
> Well, based on the 9fs test that was posted, I'd think dial is being awfully > slow. In my experience, it's almost unfailingly the DNS that slows down establishing an Internet session of any type. Lucio.

Re: [9fans] cpu command latency

2016-05-11 Thread Kenny Lasse Hoff Levinsen
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 wrote: > > >> On 11 May 2016 at 14:44, Kenny Lass

Re: [9fans] cpu command latency

2016-05-11 Thread Charles Forsyth
On 11 May 2016 at 14:44, Kenny Lasse Hoff Levinsen 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,

Re: [9fans] cpu command latency

2016-05-11 Thread Kenny Lasse Hoff Levinsen
Your loop only seems to dials the server once, then reuses the channel from /srv. 9fs(4) is just a convenience wrapper for common hosts and tasks that ultimately calls srv(4) and mount(1) as necessary - if the channel exists, it is simply a call to mount(1), which translates to an attach(5) 9P m

Re: [9fans] cpu command latency

2016-05-11 Thread arisawa
thanks charles for your quick response. the times below are mount latency just after rebooting. the first is much larger than others. 0.00u 0.00s 3.73r9fs sources 0.00u 0.00s 0.71r9fs sources 0.00u 0.00s 0.21r9fs sources with the script below: for(i in 1 2 3){

Re: [9fans] cpu command latency

2016-05-11 Thread Charles Forsyth
On 11 May 2016 at 10:04, arisawa wrote: > latency data between japan and other country will be enough. > > I want to have those times: > for(i in 1 2 3){ > time cpu -h HOST -k ‘dom=DOM’ -c pwd > sleep 3 > } > they are c > It takes ages to get throu

[9fans] cpu command latency

2016-05-11 Thread arisawa
Hello, some people say that cpu command latency will be so big that world wide grid computing using cpu command will be useless because of the latency. unfortunately I don’t have experimental data. it seems bell-labs grid servers are now closed. latency data between japan and other country will