Analyze and document RAI installation footprint
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 589
- Forks
- 76
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
RAI is a R&D framework and at the moment has a footprint which might be more suitable to run on the edge. As RAI matures, we need to take steps to map out the work needed to minimize its footprint and consider on-board deployments.
Describe the solution you'd like
An analysis of installation size and memory footprint for RAI (and its dependencies), package & feature-wise, where the current state is documented and instructions as well as an automated script to repeat the analysis is submitted in the PR.
Additionally, users need to be informed about large dependencies for core and optional packages.
Additional context
Connected to #302
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; begin by inventorying RAI and its dependencies package- and feature-wise, then measure installation size and memory footprint. Document the current results and repeatable instructions, add an automated analysis script, and identify large dependencies in core and optional packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, performance, tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100