Skip to content

Browser tests and rendezvous server #179

@litzenberger

Description

@litzenberger

Where should the rendezvous server run? We have two options:

  1. Run it on the controller VM but it looks like the latency when transferring files is included in the test.

  2. Run it on the ARM bare metal machine using the npm install --global libp2p-websocket-star-rendezvousl but this will also take away from the tests cpu cycles.

Which is preferred?

Examples of when I run the rendezvous server local vs hosted in the cloud:

┌────────────────────┬────────────────────┬──────────────────────────────────────────────────┬────────────────────┬─────────────────┐
│ Test               │ Warmup             │ Description                                      │ File Set           │ Duration        │
├────────────────────┼────────────────────┼──────────────────────────────────────────────────┼────────────────────┼─────────────────┤
│ peerTransferBrows… │ off                │ Transfer file between peers in the browser       │ OneKBFile          │ s:5 ms: 109.645 │
└────────────────────┴────────────────────┴──────────────────────────────────────────────────┴────────────────────┴─────────────────┘

local

wait
Writing output in a multiple files
┌────────────────────┬────────────────────┬──────────────────────────────────────────────────┬────────────────────┬─────────────────┐
│ Test               │ Warmup             │ Description                                      │ File Set           │ Duration        │
├────────────────────┼────────────────────┼──────────────────────────────────────────────────┼────────────────────┼─────────────────┤
│ peerTransferBrows… │ off                │ Transfer file between peers in the browser       │ OneKBFile          │ s:0 ms: 276.975 │
└────────────────────┴────────────────────┴──────────────────────────────────────────────────┴────────────────────┴─────────────────┘

Metadata

Metadata

Labels

kind/supportA question or request for support

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions