-
Notifications
You must be signed in to change notification settings - Fork 489
Open
Labels
effort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importanthelp wantedSeeking public contribution on this issueSeeking public contribution on this issuetopic/perfPerformancePerformance
Description
discussed in https://pl-strflt.notion.site/js-libp2p-perf-benchmarking-f7c42f96cbd44799a321347f6c15c8d4?pvs=4
Goals
- We would like to be able to benchmark js-libp2p across releases and compare performance, particularly across different permutations in the stack.
- Testing different transports against each other performance wise.
- We are currently having an issue with performance with [Yamux performance](Performance significantly worse than libp2p mplex ChainSafe/js-libp2p-yamux#42) and we would like to be able to nail down why there are such drastic differences.
- We have issues [sending large files](https://github.com/libp2p/js-libp2p/actions/runs/6265587906/job/17014869561?pr=2048#step:5:2415) and whilst this is cause by separate issue it would be beneficial to measure file transfer performance and have that running on CI.
### Tasks
- [ ] https://github.com/libp2p/js-libp2p/issues/1964
- [ ] https://github.com/libp2p/js-libp2p/issues/2120
- [ ] https://github.com/libp2p/test-plans/issues/307
Metadata
Metadata
Assignees
Labels
effort/daysEstimated to take multiple days, but less than a weekEstimated to take multiple days, but less than a weekexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importanthelp wantedSeeking public contribution on this issueSeeking public contribution on this issuetopic/perfPerformancePerformance
Type
Projects
Status
🧱Blocked