Expired
Milestone
Dec 8, 2020–Feb 8, 2021
signalc validation
objective
- decide whether to continue development of signalc
requirement
- prove that signalc can handle load that causes signald to suffer unacceptable message lag (or prove it can't and pivot)
benchmarks
- signalc produces message lag < 2sec 99% of the time for a channel w/ 1000 subscribers in a trial of 60 messages sent over 1 minute
status: yellow
===> BOARD <===
- points: 25
- complete: 10
- left: 15
- time: 7 weeks
- spent: 4
- left: 3 weeks
- burn rate:
- current: 2.5 points/week
- needed: 5 points/week
- projections:
- 3 points/week -> 5 weeks
- 8 points/week -> 2 weeks
All issues for this milestone are closed. You may close this milestone now.
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
8
- load: simulator can compare message lag between signald & signalc
- load: simulator can reproduce message lag in signald
- load: simulator can subscribe 1000 bots to signalboost
- signalc: handle incoming signal messages
- signalc: relay messages to/from signalboost over unix socket
- signalc: run in docker
- signalc: send a message from a number registered in a previous session (persistence)
- signalc: register a number and send a message from it (1-shot)
Loading
Loading
Loading