It improves a lot:

ZEO:             ~660μs ->  ~490μs
NEO/pylite:      ~750μs ->  ~470μs      (Cpy)
NEO/pylite:      ~500μs ->  ~370μs      (Cgo)
NEO/pysql:      ~1450μs ->  ~780μs      (Cpy)
NEO/pysql:      ~1000μs ->  ~670μs      (Cgo)
NEO/go:          ~450μs ->  ~280μs      (Cpy)
NEO/go:           ~90μs ->   ~80μs      (Cgo)
NEO/go-nosha1:    ~60μs ->   ~55μs

Same as on oct04 but now we add C-states profile. C-states are not yet disabled.

~ the same as on oct04 only we add C-states profiling. C-states are not yet disabled.

py timings improve a bit - ~15-20μs per python part (i.e. ~30-40μs if
both client and server is in python).

go-go timings stays ~ the same.

Timings are ~same as on sep17 but now a lot more info about system is
added + C-stats profile. C-states are not yet disabled.

Like info-local but about any remote deployment.

Numbers stays the same; we just added more diagnostic to log.

for ZEO and NEO/py the time over network is ~ the same as the time over just IPC on z6001 !
for Go network makes it visible slower.

Probably C-states play a big role above.

Seems to be similar to localhost on z6001 and is a bit _faster_ for cases where
ther is interprocesses communication.

This is explained by the fact that intel_idle tend not to go to deeper sleep
states whenever system loadavg increases.

Seems to be similar to localhost on neo1.

The network:

- improves much for ping (ethernet drivers are patched https://marc.info/?l=linux-netdev&m=150654466102277&w=2)
- becomes _worse_ for 1B, 1472B TCP pings
- becomes better for 4K TCP pings

The time for ZEO and NEO/* imrpoves by 100-200μs.

It has to be understood what happens with TCP and then maybe other
timings will improve more.

The network is awful - 500μs latency on non-small ping (on small ping latency is great: 33μs)