[Lambda] Display vCPU Allocation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws
- Domain
- cloud
Research direction
Start by reviewing the linked AWS Lambda memory configuration documentation and the Epsagon Lambda Memory Performance Benchmark to understand the memory-to-vCPU relationship. Done would be a visual indicator in the AWS console that communicates vCPU allocation, including the full-vCPU point around 1,769 MB.
Written by the indexing model from the issue text.
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
Provide a visual representation of the vCPU allocation for a Lambda function based on its configured memory size.
Which service(s) is this request for?
AWS Lambda
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Currently, the amount of vCPU allocated to a Lambda function is proportional to the memory configuration, as described in the AWS Lambda documentation. However, this information is not visually displayed in the AWS console, which can lead to misunderstandings among developers and management teams.
For example, while experienced AWS developers may understand this relationship, managers or supervisors might misinterpret memory usage and suggest reducing memory allocation without realizing the impact on vCPU performance. This can result in slower execution times and increased costs.
A visual indicator, such as a progress bar or percentage display showing the vCPU allocation (e.g., full vCPU at 1,769 MB), would improve clarity for all stakeholders. It would facilitate discussions with management, enhance developers' understanding, and reduce incorrect optimization actions.
Are you currently working around this issue?
To address this, we rely on documentation and tools like Epsagon's Lambda Memory Performance Benchmark to validate the relationship between memory and vCPU allocation. However, these methods require additional effort and are not integrated into the AWS console.
Additional context
This feature would align with AWS's goal of providing intuitive and transparent tools for developers and organizations. It would also reduce the need for external tools and documentation references, streamlining the optimization process for Lambda functions.
Attachments
N/A
- Dominant language
- No language data
- Stars
- 196
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
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.
More from aws/aws-lambda-roadmap
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-lambda-roadmap#101 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
aws/aws-lambda-roadmap#100 ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
aws/aws-lambda-roadmap#97 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-lambda-roadmap#96 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-lambda-roadmap#95 · 1 comment · 1 reaction ·
All issues in aws/aws-lambda-roadmap
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug needs-triage service/elbv2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hashicorp/terraform-provider-aws#50100 · 1 comment ·