Investigate the impact of endpoint startup time on AWS Lambda that are executed infrequently

[lailabougria]

There are cases in which a system has AWS Lambdas that are executed infrequently. We'd like to investigate the impact endpoint startup time may have on these cases.

A possible avenue is to investigate is to spike whether some of the work that's currently performed during startup (e.g. assembly scanning for message and handler types, composing receive pipeline) could be done at compile-time instead to reduce cold-start times.

When it comes to AWS, there is anecdotal evidence that Lambda instances are not started and stopped on each invocation, it's not officially documented, though.

Triage

This triage checklist should be filled in by a staff member from Particular Software.

Yes / No	Triage criteria
No	The expected effort to code and document the enhancement is less than 8 hours.
No	A reviewer can approve any changes in less than 1 hour.
No	The solution is obvious and does not require analysis by a task force.
No	The issue is NOT blocking the customer from using the Preview in production.
No	The issue is blocking the user from using the Preview in production.
No	There's evidence solving the problem will benefit multiple users.