public/obsidian-livesync
1
0
Fork 0
mirror of https://github.com/vrtmrz/obsidian-livesync.git synced 2026-07-13 00:03:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Document CLI benchmark comparison model

Browse Source
This commit is contained in:
vorotamoroz
2026-07-08 07:03:23 +00:00
parent 870ac93cac
commit 33cd6a3b51
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/bench-network/README.md
+14
View File
@@ -50,6 +50,20 @@ this Compose package it is not a real smartphone tethering/VPN measurement; it
uses the local Compose network. Use it only for wiring checks unless the runner uses the local Compose network. Use it only for wiring checks unless the runner
is executed in an actual tethered/VPN environment. is executed in an actual tethered/VPN environment.
## Comparison model
The primary local comparison is between a remote-database path and a direct P2P
path:
| Case | Data path | What is measured | What is not measured |
| --- | --- | --- | --- |
| `couchdb-baseline` | Device A -> CouchDB -> Device B | Two one-shot CLI synchronisation commands through a local HTTP latency proxy | Real WAN jitter, packet loss, bandwidth limits, VPN encapsulation, and server contention |
| `p2p-direct-local` | Device A -> Device B after Nostr signalling | One CLI P2P synchronisation command over WebRTC DataChannel with TURN disabled | Public relay operation, mobile carrier behaviour, TURN relay throughput, and first-peer discovery latency |
Use the CouchDB result as the remote-store baseline and the P2P result as the
direct-transfer comparison. The Nostr relay is used for signalling in the P2P
case, but synchronised note content is transferred over the WebRTC DataChannel.
## Dataset and latency controls ## Dataset and latency controls
```bash ```bash