spcl / spcl/serverless-benchmarks
Optimize C++ deployments
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 199
- Forks
- 105
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we copy all dynamic libraries from dependencies into the final deployment image. This is not optimal - AWS Lambda deployment script uses ldd to recursively find only those shared libraries, that are actually used by the binary. We could apply the same to optimize container size.
The same happens for code packages - we don't need to pack and deploy system libraries, which we know will be available on Lambda; we should only pack our dependencies from /opt/.
For arm64 (#265), we can use an ldd replacement.
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
Start with the AWS Lambda deployment script and trace how dynamic libraries and code packages are copied into the final deployment image. Compare the existing dependency handling with recursive ldd lookup, limiting packaged system libraries while retaining dependencies from /opt/. For arm64, evaluate the linked cross-compile-ldd replacement; done means smaller deployments containing only required libraries and packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, cpp
- Domain
- cloud, devops, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100