- 28 Sep, 2017 1 commit
-
-
Kirill Smelkov authored
-
- 20 Sep, 2017 4 commits
- 19 Sep, 2017 5 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
200μs of NEO/go without sha1 case is still questionable: T(transmit request) = 10μs (deco rx throttle) + t(link-tx-request) T(transmit answer) = 10μs·4.5 (~ 4.5 KB answer for 4K ZData) + teco.rx-delay (= 3μs ?) || vv T(link) ~= 60μs T(teco-local,no-sha1,NEO/go) was ~= 100μs (see time-sep17-teco.txt) T(deco-local,no-sha1,NEO/go) was ~= 20μs (see time-sep17-deco.txt) || vv T(teco-deco,no-sha1,NEO/go) = 100μs/2 + 20μs/2 = 60μs ? if so RTT(getobject) should be 60+60 = 120μs but we have 200μs.
-
Kirill Smelkov authored
-
- 18 Sep, 2017 22 commits
-
-
Kirill Smelkov authored
Something is wrong with the network: ping latency is 110μs but go-go time is ~ 360μs which is not the same as 110 + 100 (go-go time on teco; on deco it is 30 and it should be even less: 100/2 + 30/2). Will investigate.
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
- 17 Sep, 2017 4 commits
-
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
- 15 Sep, 2017 4 commits
-
-
Kirill Smelkov authored
With some care it is possible for serveRecv to put itself to pause and handoff execution to goroutine for which a packet arrived. See comments in serveRecv about how it is done. For BenchmarkTCPlosr cuts RTT 12.5μs -> 6.6μs .
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-
Kirill Smelkov authored
-