Skip to content
This repository has been archived by the owner on Apr 16, 2020. It is now read-only.

Issues: ipfs-inactive/ipfs-performance-profiling

12 Open 1 Closed
12 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

I measured the data, but I don't know what it means. question
#14 opened Jan 16, 2019 by zcyzhu
1
Option to run the benchmarks in the browser as well.
#11 opened Apr 12, 2017 by daviddias
Setup needs support benchmarks with multiple nodes.
#10 opened Apr 12, 2017 by daviddias
Move profile to the top
#9 opened Apr 12, 2017 by daviddias
npm run benchmarks:report:profile runs two times
#8 opened Apr 12, 2017 by daviddias
profiling should default to js-ipfs core only
#7 opened Apr 12, 2017 by daviddias
Needs a way to log out reports and to compare them
#6 opened Apr 12, 2017 by daviddias
update aegir for latest standardJS compliance
#5 opened Apr 12, 2017 by daviddias
make it a cli
#4 opened Apr 12, 2017 by daviddias
could suite name just be the name of the file?
#3 opened Apr 12, 2017 by daviddias
move suites folder out of src to make it path independent of the module
#2 opened Apr 12, 2017 by daviddias
Error on npm run benchmark bug
#1 opened Apr 12, 2017 by daviddias
1
ProTip! Follow long discussions with comments:>50.