dwyl/learn-aws-lambda

Experiment: should we use Lodash in Lambda Functions?

Open

#67 opened on Feb 16, 2016

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

Description

JSPerf suggests that lodash _.map is faster than native Array.map https://jsperf.com/native-map-vs-lodash-map but is there an overhead in loading lodash for a single execution? is it enough to offset the Performance benefits of the module?

Contributor guide

Tech stack
javascriptnodejsaws
Domain
backendperformance
Issue type
research
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.
1-3 hours
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
javascriptaws lambdaperformance testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate the performance trade off between using lodash's .map vs native Array.map in AWS Lambda functions. Start by reading the linked jsperf results. Then set up a simple Lambda function that benchmarks both approaches with realistic data sizes, measuring execution time and cold start overhead. Consider the size of lodash bundle and its impact on Lambda cold starts. Document findings and provide a recommendation. No existing PRs or comments to build upon.