pmndrs/use-cannon

Create stress-testing benchmarks for targeting performance improvements

Open

#62 opened on Apr 3, 2020

View on GitHub
 (0 comments) (2 reactions) (0 assignees)TypeScript (164 forks)github user discovery
help wanted

Repository metrics

Stars
 (2,950 stars)
PR merge metrics
 (PR metrics pending)

Description

In order to pursue performance improvements in both use-cannon and cannon-es, we should develop a set of benchmarks to stress-test the libs

Contributor guide

Research direction
Review existing benchmark frameworks (e.g., benchmark.js) and set up a suite that stress tests the library's performance under various physics scenarios. Focus on measuring frame rates and physics step times.
Tech stack
typescriptreact
Domain
frontend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75