Now it’ll outpout an error message when it fails due to timeout
Not the most visible message
vac:tke:
admin/misc:
Matty Handoff document finished and share with team on Wed (@Matty)
Team Lead Evaluation Criteria finished and share with team on Wed (@Matty)
Strengths and development areas for Frederico and Martin, shared with Corey, Daniel, and Jarrad (@Matty)
codex:economic-analysis
finalize all Codex notion including Dragan’s comments to litepaper (@Matty)
Wednesday call with Codex team get in sync on next steps
status:SNT-staking
staking contract implementation becoming a priority, refresh latest progress with SC team (@Martin)
nomos:economic-analysis
Reading whitepaper and updating TDC (@Frederico)
Porting wealth concentration simulation code to GPU to decrease runtimes (@Frederico)
waku:economic-analysis
Continue Waku Network of Networks design discussion with Franck, concerns around forking (@Martin)
Research similar abstract p2p validation protocols (e.g. former Keep Network)
vac:dst:
eng-10ktool:vac:bandwidth-test
Try to get a stable nim-libp2p version for simulations. Investigated with Alex about building issues with nimble.
Analized libp2p metrics, everything normal so far
call with p2p team
Scale testing for 10K project
setup go-waku experiment at scale
Successfully simulated a 2,150 node simulation and gathered some basic metrics
Modified Kubernetes to allow for more pods to allow for (in theory) scaling to 10k+
Failed simulations at 10000 and 5000 nodes - current limits seem to be around ~4800 or so
Prometheus is a definite bottleneck - need to switch to a scaled/sharded Prometheus/Thanos setup
Attempting one last simulation over the weekend at 4200 nodes
Diagnosing 10K project bottlenecks
Identified a major potential bottleneck in the form of control plane traffic going over Wireguard / large packet load over WG causing swarm collapse
will test the new theory later by re-deploying on Vac Kubernetes with a local control plane + local traffic (while still complying with infra team requirements)