ipfs/kubo

add long running network tests that test different workloads

Open

#2,056 建立於 2015年12月11日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)Go (13,906 star) (2,725 fork)batch import
help wantedkind/test

描述

This means for example adding and catting different things, of different sizes.

This could use docker.

This could allocate a couple of machines to it, for 10-20min, and we could have travis machines start up + participate and shut down, etc.

Scripts could randomly add + pull things over time, simulating use. Scripts could go through heavy spikes of traffic, etc.

Long running tests would have to report stats to a master process that tracks + logs everything and that can be explored over time.

Rather than a test "succeeding" or "failing" we would see metrics like "avg time to completing a block download" or network bandwidth breakdowns (by subprotocol, etc).

貢獻者指南

技術棧
godocker
領域
testingperformanceobservability
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
needs investigation
前置要求
Go programmingDockerdistributed systems testingmetrics collection
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Investigate the existing test framework in the repository (e.g., test/ or scripts/ directories) to understand how it runs and reports results. Look at Docker related files for potential setup. The issue suggests using random workloads and reporting metrics; consider implementing a simple prototype that simulates adding and retrieving data with varying sizes and measures timings. Check if there are any design documents or discussions in the repo about distributed testing infrastructure. The lack of maintainer input on this old issue means you would need to propose a design before implementing.