AWS Lambda Power Tuning

AWS Lambda Power Tuning is an AWS Step Functions state machine that helps you optimize your Lambda functions in a data-driven way.

The state machine is designed to be quick and language agnostic. You can provide any Lambda function as input and the state machine will run it with multiple power configurations (from 128MB to 3GB), analyze execution logs and suggest you the best configuration to minimize cost or maximize performance.

The input function will be executed in your AWS account - performing real HTTP calls, SDK calls, cold starts, etc. The state machine also supports cross-region invocations and you can enable parallel execution to generate results in just a few seconds. Optionally, you can configure the state machine to automatically optimize the function and the end of its execution.

Last but not least, the state machine will generate a dynamic visualization of average cost and speed for each power configuration (more details below):

How to deploy the state machine

There are a few options documented here.

How to execute the state machine

You can execute the state machine manually or programmatically, see the documentation here.

State Machine Input and Output

Here's a typical execution input with basic parameters:

{
    "lambdaARN": "your-lambda-function-arn",
    "powerValues": [128, 256, 512, 1024],
    "num": 50,
    "payload": {}
}

Full input documentation here.

The state machine output will look like this:

{
  "results": {
    "power": "128",
    "cost": 0.0000002083,
    "duration": 2.906,
    "stateMachine": {
      "executionCost": 0.00045,
      "lambdaCost": 0.0005252,
      "visualization": "https://lambda-power-tuning.show/#<encoded_data>"
    }
  }
}

Full output documentation here.

Statistics visualization

You can visually inspect the tuning results to identify the optimal tradeoff between cost and performance.

The data visualization tool has been built by the community: it's a static website deployed via AWS Amplify Console and it's free to use.

If you don't want to use the visualization tool, you can simply ignore the stateMachine.visualization output. No data is ever shared or stored by this tool.

Website repository: matteo-ronchetti/aws-lambda-power-tuning-ui

Optionally, you could deploy your own custom visualization tool and configure the CloudFormation Parameter named visualizationURL with your own URL.

Additional features, considerations, and internals

Here you can find out more about some advanced features of this project, its internals, and some considerations about security and execution cost.

CHANGELOG (SAR versioning)

From most recent to oldest, with major releases in bold:

• 3.3.3 (2020-07-17): payload logging bugfix for pre-processors
• 3.3.2 (2020-06-17): weighted payloads bugfix (for real)
• 3.3.1 (2020-06-16): weighted payloads bugfix
• 3.3.0 (2020-06-10): Pre/Post-processing functions, correct regional pricing, customizable execution timeouts, and other internal improvements
• 3.2.5 (2020-05-19): improved logging for weighted payloads and in case of invocation errors
• 3.2.4 (2020-03-11): dryRun bugfix
• 3.2.3 (2020-02-25): new dryRun input parameter
• 3.2.2 (2020-01-30): upgraded runtime to Node.js 12.x
• 3.2.1 (2020-01-27): improved scripts and SAR template reference
• 3.2.0 (2020-01-17): support for weighted payloads
• 3.1.2 (2020-01-17): improved optimal selection when same speed/cost
• 3.1.1 (2019-10-24): customizable least-privilege (lambdaResource CFN param)
• 3.1.0 (2019-10-24): $LATEST power reset and optional auto-tuning (new Optimizer step)
• 3.0.0 (2019-10-22): dynamic parallelism (powerValues as execution parameter)
• 2.1.3 (2019-10-22): upgraded runtime to Node.js 10.x
• 2.1.2 (2019-10-17): new balanced optimization strategy
• 2.1.1 (2019-10-10): custom domain for visualization URL
• 2.1.0 (2019-10-10): average statistics visualization (URL in state machine output)
• 2.0.0 (2019-07-28): multiple optimization strategies (cost and speed), new output format with AWS Step Functions and AWS Lambda cost
• 1.3.1 (2019-07-23): retry policies and failed invocations management
• 1.3.0 (2019-07-22): implemented error handling
• 1.2.1 (2019-07-22): Node.js refactor and updated IAM permissions (added lambda:UpdateAlias)
• 1.2.0 (2019-05-24): updated IAM permissions (least privilege for actions)
• 1.1.1 (2019-05-15): updated docs
• 1.1.0 (2019-05-15): cross-region invocation support
• 1.0.1 (2019-05-13): new README for SAR
• 1.0.0 (2019-05-13): AWS SAM refactor (published on SAR)
• 0.0.1 (2017-03-27): previous project (serverless framework)

Contributing

Contributors and PRs are always welcome!

Tests and coverage

Install dev dependencies with npm install --dev. Then run tests with npm test, or coverage with npm run coverage.