ostenbom / refunction Goto Github PK

View Code? Open in Web Editor NEW

20.0 20.0 1.0 22.83 MB

Reusing containers for faster serverless function execution - Masters Project @ Imperial College

License: GNU Affero General Public License v3.0

Go 63.34% Dockerfile 0.60% Makefile 0.80% C 31.00% Shell 0.65% Python 1.68% Java 1.55% JavaScript 0.38%

containerd containers criu serverless

refunction's People

Contributors

Stargazers

Watchers

Forkers

zayat

refunction's Issues

Refunction setup steps

Hi, I am interested in this project. Is it possible that you provide a detailed setup guide for refunction? Currently I am not able to run the program.

Maybe there is a mistake in the report of how CRIU restore pid

https://criu.org/Pid_restore

I think the method is stupid, so I look up the code of CRIU. And there aren't any fork() there.

Question - Restoring from check-point

Serverless environments keep functions warm for some undefined period of time after the initial cold start. Optimizations take advantage of this time period of punctuated statefulness. For example a database connection can be initiated once and reused, an file can be loaded into memory an re-used vs being loaded for every execution.

Can your technique be used to extend this statefulness beyond this undefined warm period with some kind of check-pointing scheme? It seems it would work well for the file-io example not so much for the database connection.

Recommend Projects