Measure cached Dosh attach fast path
This commit is contained in:
@@ -27,13 +27,19 @@ Reported metrics:
|
||||
| Metric | Meaning |
|
||||
| --- | --- |
|
||||
| `ssh_true_ms` | Time to run `ssh host true` with the same key/options. |
|
||||
| `dosh_attach_ms` | Time for `dosh-client --attach-only` to render the first frame and detach. |
|
||||
| `dosh_attach_ms` | Time for `dosh-client --attach-only` to render the first frame and detach on the configured path. With `--no-cache`, this is cold SSH bootstrap plus UDP attach. |
|
||||
| `dosh_cached_attach_ms` | Time for a warmed Dosh client to attach using cached UDP credentials/tickets, render the first frame, and detach. This is the fast-path claim and should be approximately network RTT plus local process/render overhead. |
|
||||
| `mosh_start_true_ms` | Time for `mosh host -- true` to bootstrap, run `true`, and exit. |
|
||||
|
||||
These are not identical workloads. They are still useful because they measure the
|
||||
startup path each tool must pay before useful remote work begins. Public numbers
|
||||
must include the command, machine, OS, CPU, network path, and sample count.
|
||||
|
||||
Do not cite cold `dosh_attach_ms` as the core speed claim. Cold Dosh still pays SSH
|
||||
startup/authentication. Cite `dosh_cached_attach_ms` for repeat attach/reconnect
|
||||
speed, and cite cold `dosh_attach_ms` only to show that fallback remains competitive
|
||||
with ordinary SSH.
|
||||
|
||||
## Feature Matrix
|
||||
|
||||
| Feature | Mosh | Dosh now | Public status |
|
||||
|
||||
Reference in New Issue
Block a user