Serverless logo
Products
FRAMEWORK
Overview
CI/CD
Secrets
Plugins
Pricing
Signup
CONSOLE
Overview
Pricing
Signup
CLOUD
Overview
Pricing
FAQ
Signup
Docs
FRAMEWORK
Documentation
Getting Started
CLOUD
Documentation
Getting Started
CONSOLE
Documentation
Getting Started
Pricing
Company
ABOUT US
About
Careers
Contact Us
SUPPORT
Get Support
COMMUNITY
Slack
Forum
Partners
Meetups
LEARN
Blog
Examples
Guides
LoginTry Console
Serverless logo
SalesLog in
Sign Up
Products
FRAMEWORK
Overview
CI/CD
Secrets
Plugins
CONSOLE
Overview
Signup
CLOUD
Overview
FAQ
Signup
Docs
FRAMEWORK
Overview
Get Started
CLOUD
Overview
Get Started
Pricing
Company
ABOUT US
Careers
Blog
About
Partners
LEARN
Guides
Examples
CONTACT US
Contact Us
Premium Support
COMMUNITY
Slack
Meetups
Forum
Support
Serverless Console - Docs

Serverless Console – Documentation

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Item title

Item description

X
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Item title

Item description

Serverless logo
Product
Expand
Option 1Option 2Option 3
DocsPricing
Company
Expand

Feature 1

Lorem ipsum dolor emet sin dor lorem ipsum

Feature 2

Lorem ipsum dolor emet sin dor lorem ipsum

Feature 3

Lorem ipsum dolor emet sin dor lorem ipsum

Feature 4

Lorem ipsum dolor emet sin dor lorem ipsum
Search
Sales & Support
LoginSign Up
Open MenuClose Menu
Go to GitHub
Home
How it Works
Development Workflows
Building Applications
Link 1Link 1Link 1
Building Applications
Link 1Link 1Link 1
Building Applications
Link 1Link 1Link 1
Automated Testing
CLI Reference

Duration

The term duration is used in a variety of scenario and charts within Serverless Console. This helps provide a glossary of terms, and explains what is included, or excluded when looking at duration values in Serverless Console charts and interfaces.

Understanding Duration Across Console

Applying these definitions, you can expect the following behavior and details are included across Console.

On the Metrics View The red number and dots represent the slowest 5% of transactions that occurred during the time frame selected. This does not include Cold Starts.

The black number and line describe the average Duration for the selected time frame. This does not include Cold Starts.

On the Explorer When the Trace is first received the value shown, is the Trace Duration of your function and does not yet include Extension Duration. A few seconds after the Trace is received we receive the full duration details and show the full duration with any Cold Starts duration. The max value progress bar is calculated based on the 5% slowest duration during the time frame to help show relative performance of the trace.

On Trace Detail View The Duration shown in the header represents the execution time of your function plus the duration of any execution time of any Lambda Extensions including the Serverless Console Extension.

The span chart is based on the start and end times collected from the Open Telemetry trace, plus the recorded Cold Start if one occurred. It does not include Lambda Extension Execution Times and is therefore not \directly related to Billed Duration.

When Filtering Filtering is based on the Duration of your function, pluse the duration of any Lambda Extensions including the Serverless Runtime OTEL Extension.

When Calculating Cost Cost is calculated based on Billed Duration.

Optimizing Initialization in AWS Lambda

Initialization includes the following:

  • Initializing all External AWS Lambda Extensions configured on the function (there is a limit of 10 Extensions per function).

  • Initializing the AWS Lambda Runtime (e.g, Node.js, Python).

  • Initializing the AWS Lambda Function code.

You will want to optimize Initialization performance as best you can. Poor Initialization performance will directly affect the experience of your users and customers. Additionally, it's important to note that AWS charges you for Initialization time. Unfortunately, no tooling can offer a breakdown of what happens within the Initialization phase of AWS Lambda. Generally, adding multiple Extensions, large code file sizes, and using a slower runtime (e.g., Java) are the biggest culprits when it comes to slow Initialization.

Once initialized, each instance of your function can process thousands of requests without performing another Initialization. However, AWS Lambda function instance containers will shutdown within 5-15 minutes of inactivity. After that, the next event will be a Cold-Start, causing Initialization to run again.

Configuring Timeouts in AWS Lambda

It's important to note that your function's timeout setting limits the duration of the entire Invocation phase. For example, if you set the function timeout as 360 seconds, the function and all extensions need to complete within 360 seconds.

Extensions and the Invocation Phase

The Invocation phase is comprised mostly of your handler (i.e. your business logic), and you want to optimize that as best you can because its performance (combined with Initialization performance) will have the biggest impact on the experience for your users and customers.

  • Running External Extensions in parallel with the function. These also continue running after the function has completed, enabling Serverless Console to capture diagnostic information and ingest metrics, traces and logs.

  • Running the wrapper logic for Internal Extensions.

  • Running the handler for your AWS Lambda.

Edit this page
Serverless logo
Product
Expand
Option 1Option 2Option 3
DocsPricing
Company
Expand

Feature 1

Lorem ipsum dolor emet sin dor lorem ipsum

Feature 2

Lorem ipsum dolor emet sin dor lorem ipsum

Feature 3

Lorem ipsum dolor emet sin dor lorem ipsum

Feature 4

Lorem ipsum dolor emet sin dor lorem ipsum
Search
Sales & Support
LoginSign Up
Open MenuClose Menu
FRAMEWORK
Overview
CI/CD
Secrets
Plugins
Pricing
CONSOLE
Overview
Pricing
Signup
RESOURCES
Framework DocsConsole DocsGuidesExamplesBlog
COMMUNITY
SlackMeetupsForum
SUPPORT
Contact UsPremium Support
COMPANY
AboutCareersPartners
Join our monthly newsletter
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
© 2022 Serverless, Inc. All rights reserved.
Terms of ServicePrivacy Policy