dwyl/learn-aws-lambda

can we draw a graph of resource usage (thus cost) and execution time?

Open

#74 opened on Apr 26, 2016

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (1,037 stars) (206 forks)batch import
enhancementhelp wantedquestion

Description

Comparison of resources allocated to lambda:

geo-indexer-128mb geo-indexer-512mb geo-indexer-1500mb

Contributor guide

Tech stack
javascriptaws
Domain
cloudperformanceobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
AWS Lambda basicsNode.jsCloudWatch metrics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate how to retrieve AWS Lambda execution time and allocated memory from CloudWatch metrics. Consider using AWS SDK to fetch data and create a chart (e.g., using D3.js or a simple HTML canvas). The issue body shows three images with different memory settings, suggesting a need to plot cost (proportional to memory * time) vs execution time. Look at existing examples in the repository or AWS documentation. Since this is a learning repo, the result could be a new page or section in the README.