mirror of
https://github.com/tailscale/tailscale.git
synced 2026-06-03 21:01:54 +08:00
e8be3b7989
In order to allow us to measure the performance effects of client-side netmap caching, both with and without the feature enabled, add logs to record how long it takes after a client restart or profile switch for the node to establish contact with peers, relative to the first uncached netmap. We do this by keeping track of a timestamp when the connection is constructed, and logging a record for "new" peer contacts that records how long (in microseconds) it took from the time the peer was recorded as a candidate. The message includes whether the contact was via DERP or direct, and whether a cached netmap was in use at the time. This builds on and extends the counters from #19699, but here we include new contacts whether or not a cached netmap is in use, so that we can establish a baseline for comparison. Updates #12639 Updates tailscale/projects#27 Change-Id: I4f6d050e221f3881848d05a0425c4a5d1a59294c Signed-off-by: M. J. Fromberger <fromberger@tailscale.com> |
||
|---|---|---|
| .. | ||
| blockforever_conn.go | ||
| debughttp.go | ||
| debugknobs_stubs.go | ||
| debugknobs.go | ||
| derp_test.go | ||
| derp.go | ||
| disco_atomic_test.go | ||
| disco_atomic.go | ||
| discopingpurpose_string.go | ||
| endpoint_default.go | ||
| endpoint_stub.go | ||
| endpoint_test.go | ||
| endpoint_tracker_test.go | ||
| endpoint_tracker.go | ||
| endpoint.go | ||
| magicsock_default.go | ||
| magicsock_linux_test.go | ||
| magicsock_linux.go | ||
| magicsock_notplan9.go | ||
| magicsock_plan9.go | ||
| magicsock_test.go | ||
| magicsock.go | ||
| peermap_test.go | ||
| peermap.go | ||
| peermtu_darwin.go | ||
| peermtu_linux.go | ||
| peermtu_stubs.go | ||
| peermtu_unix.go | ||
| peermtu.go | ||
| rebinding_conn.go | ||
| relaymanager_test.go | ||
| relaymanager.go | ||