Skip to content

A guide to automatically priming Java applications ready for snapshotting (CRaC/Lambda SnapStart)

License

Notifications You must be signed in to change notification settings

marksailes/snapstart-priming-guide

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Lambda SnapStart Priming Guide

Goal

This guide aims to explain techniques for priming Java applications. It assumes a base understanding of AWS Lambda, Lambda SnapStart, and CRaC.

Introduction to Lambda SnapStart

Lambda SnapStart is a performance optimization feature. It reduces the amount of time it takes to return a response to the caller when a new execution environment has been created (cold start). At deployment time, it creates an execution environment and loads your code into it. Once the init phase has completed it takes a snapshot of the entire FireCracker microVM. This includes processes, memory, and any files on the file system. The snapshot is encrypted and placed in persistent storage. Then when future execution environments are required, they can be restored from the snapshot instead of being created from scratch. To further improve the restore time, snapshots are cached.

Read the rest at my blog

About

A guide to automatically priming Java applications ready for snapshotting (CRaC/Lambda SnapStart)

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published