#450
[Enhancement]: compact size
Target Component
Documentation and User Experience
Enhancement Description
$ find . -type f -exec du -h {} + | sort -hr | head -n 10 61M ./.git/objects/pack/pack-8ae1a7ec5efb2cb19ad6e2d88fa945a9182180f3.pack 28M ./observability/jaeger/bin/jaeger-clickhouse-linux-amd64 27M ./observability/jaeger/bin/jaeger-clickhouse-linux-arm64 8.2M ./frontend/public/fonts/NotoSansSC-Bold.otf 8.0M ./frontend/public/fonts/NotoSansSC-Regular.otf 3.0M ./examples/neo4j/plugins/apoc-5.26.19-core.jar 1.5M ./backend/pkg/graph/generated.go 612K ./frontend/src/graphql/types.ts 564K ./frontend/public/fonts/NotoSans-Bold.ttf 556K ./frontend/public/fonts/NotoSans-Regular.ttf
Technical Details
No response
Designs and Mockups
- Make a shell script, The agent automatically download jaeger-clickhouse from [https://github.com/jaegertracing/jaeger-clickhouse/releases]
- Make a pre compile script, download the front.
Alternative Solutions
No response
Verification
- I have checked that this enhancement hasn't been already proposed
- This enhancement aligns with PentAGI's goal of autonomous penetration testing
- I have considered the security implications of this enhancement
- I have provided clear use cases and benefits
Shipping 55MB of jaeger-clickhouse binaries in the repo is indeed painful — it bloats clones and makes every PR diff noisy. Downloading the release artifact at setup time is a good call, but I'd suggest:
The .git pack is 61MB which suggests a rewrite of git history might be worth considering separately (e.g. git-filter-repo) if the repo is still early-stage.